October 2012 - logback-user

Logback JNDI context selector with file system config file
by Kevin Rohr 31 Oct '12

31 Oct '12

Why is it the case that if I use JNDI context selector, the configuration file must be loaded from the classpath? This is problematic for me, because although it allows me to load the file that I want, I cannot make changes to the file on the fly (JBoss sucks the file in memory on startup), which is one of the most important features of logback to me. -- Kevin Rohr (440) 522-0880 kevinmrohr(a)gmail.com

1 0

logback-android: How to suppress bootstrap messages?
by cowwoc 31 Oct '12

31 Oct '12

Hi, When I launch an application using logback-android I get the following logs at startup: 10-30 13:03:41.341: I/System.out(1022): 13:03:39,311 |-WARN in ch.qos.logback.classic.LoggerContext[default] - No config in SD card 10-30 13:03:41.341: I/System.out(1022): 13:03:39,314 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [AndroidManifest.xml] at [jar:file:/data/app/com.foo-1.apk!/AndroidManifest.xml] 10-30 13:03:41.341: I/System.out(1022): 13:03:40,178 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [assets/logback-test.xml] 10-30 13:03:41.341: I/System.out(1022): 13:03:40,179 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [assets/logback.xml] at [jar:file:/data/app/com.foo-1.apk!/assets/logback.xml] 10-30 13:03:41.341: I/System.out(1022): 13:03:40,182 |-INFO in ch.qos.logback.core.joran.spi.ConfigurationWatchList@411f2f88 - URL [jar:file:/data/app/com.foo-1.apk!/assets/logback.xml] is not of type file 10-30 13:03:41.341: I/System.out(1022): 13:03:41,072 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set 10-30 13:03:41.341: I/System.out(1022): 13:03:41,072 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.android.LogcatAppender] 10-30 13:03:41.341: I/System.out(1022): 13:03:41,073 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [logcat] 10-30 13:03:41.341: I/System.out(1022): 13:03:41,091 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 10-30 13:03:41.341: I/System.out(1022): 13:03:41,245 |-INFO in ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Adding LoggerContextListener of type [ch.qos.logback.classic.jul.LevelChangePropagator] to the object stack 10-30 13:03:41.341: I/System.out(1022): 13:03:41,246 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@4123c198 - Propagating DEBUG level on Logger[ROOT] onto the JUL framework 10-30 13:03:41.341: I/System.out(1022): 13:03:41,247 |-INFO in ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Starting LoggerContextListener 10-30 13:03:41.351: I/System.out(1022): 13:03:41,247 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to WARN 10-30 13:03:41.351: I/System.out(1022): 13:03:41,247 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@4123c198 - Propagating WARN level on Logger[ROOT] onto the JUL framework 10-30 13:03:41.351: I/System.out(1022): 13:03:41,247 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [logcat] to Logger[ROOT] 10-30 13:03:41.351: I/System.out(1022): 13:03:41,248 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. 10-30 13:03:41.351: I/System.out(1022): 13:03:41,249 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@4127e938 - Registering current configuration as safe fallback point Is there a way to suppress these logs unless a configuration problem is encountered? Thanks, Gili -- View this message in context: http://old.nabble.com/logback-android%3A-How-to-suppress-bootstrap-messages… Sent from the Logback User mailing list archive at Nabble.com.

2 2

Logging to a network file system
by Scott Ruch 29 Oct '12

29 Oct '12

Apologies if this has already been discussed. I tried searching the list archive but I didn't find anything similar. I've been required to start logging to a network file system and I wanted to find out what the best practices were for logback in this scenario. (IMO, "best practice" would be to not log to a network file system but that's not my decision.) I've read through the documentation on the AsyncAppender and that is the direction I am evaluating. Any other suggestions would be appreciated. Thanks, Scott

3 2

Issue with PropertyDefinerBase
by Basu 29 Oct '12

29 Oct '12

Hi, I have been trying to setup a property 'applicationUrl' which can be evaluated at runtime. I have created the PropertyConfigurer as below: public class LogbackApplicationURLPropertyDefiner extends PropertyDefinerBase { public String getPropertyValue() { LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory(); lc.putProperty(); return ( UserContext.getUserContext() == null ? "User context was null, application url could not be determined" : UserContext.getUserContext().getApplicationUrl() ); } } and in the xml as: <define name="applicationUrl" class="com.iblogix.analytic.logging.LogbackApplicationURLPropertyDefiner"/> But it looks like the value is evaluated only once during the logback configruation. What I want is that the value be evaluated everytime it is acessed by someone. Is that possible using what i have right now? Thanks, Basu

1 0

Logging to stderr and stdout
by Steve Ramage 26 Oct '12

26 Oct '12

I had a question about the conventions of logging. We have an application scientific in nature, and basically it runs some process for some amount of time, and then finishes with it's output. All output in the program is driven by logback, and we generally hide the complexity of logback from our users, and support very limited configuration as needed. One issue is where error and warning messages should go for users. One argument is that they should go to stderr. stdout should have INFO, DEBUG, and TRACE. There doesn't seem to be an easy way to do this in logback. Another argument is that they should go to stderr. stdout should also have them, but also INFO, DEBUG, and TRACE. If the user is running directly then both get spammed together. A final option is they should all go to stdout, as these are all log messages, and there is no need to split them Now this isn't so much a religious argument, we are just more wondering what the conventions were, as we would like to follow them as much possible. Thanks, Steve Ramage

3 2

[logback-access] How to create access logs for NanoHTTPD by logback-access?
by Michael Zhilin 22 Oct '12

22 Oct '12

Hi, We're using NanoHTTPD and logback for several our applications. Logback provides fine logging and we like it. But now we need to add access logs. I see that logback-access module is provided for access logs, but it supports only Tomcat and Jetty. Is there way to use logback-access for NanoHTTPD access logs? Thank you in advance, Michael

1 0

Using Logback with RabbitMQ
by Smith, Larry (ECS - Enterprise Cloud Service) 20 Oct '12

20 Oct '12

Hi all, Tried looking this up on the net, but there is nothing recent. I would like to use an appender (standard or custom) that could interface with RabbitMQ. I have a need to see logging data in real time, but cannot use the console nor a database. I would assume that a custom appender can be written to communicate with the RabbitMQ exchange, and I would also like to be able to disable the appender when it is not required. Any ideas on how to begin this? Larry Smith

2 1

How to configure error handler for file appender
by Mayur Gupta 16 Oct '12

16 Oct '12

Hey Guys, Can anybody tell me how to configure a errorHandler in logback? Below is my log4j configuration: <appender name="FILE" class="org.apache.log4j.DailyRollingFileAppender"> <errorHandler class="org.apache.log4j.varia.FallbackErrorHandler"> <root-ref/> <appender-ref ref="CONSOLE"/> </errorHandler> <param name="File" value="../logs/b.log"/> <param name="Append" value="true"/>  <param name="DatePattern" value="'.'yyyy-MM-dd"/> <layout class="org.apache.log4j.PatternLayout">  <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/> </layout> </appender> Thanks -Mayur

1 0

Usage of syslog4j with log back
by Sumanth MS 12 Oct '12

12 Oct '12

Hello, I am a new logback user and am using logback for my logging. I wanted to use syslog4j to natively log to syslog.(as I do not want to open up the udp port for logging into syslog). Can I use syslog4j as an appender to logback? If not, is there any other way of using logback to log into syslog without opening up the udp port i.e. using native unix sockets! Thanks and Best Regards Sumanth

1 0

logback printing log entries out of order
by David Tkaczyk 11 Oct '12

11 Oct '12

Has anyone ever seen this behavior before: 2012-10-11 16:48:04.418 ALWAYS [Thread-1] camiant.services.qp.AbstractQPInfoImpl$EventListenerWorker.run:247 - AbstractQPInfoImpl.EventListenerWorker shutdown complete. 2012-10-11 16:48:04.415 ALWAYS [Thread-4] camiant.backout.utils.FileProgressIndicator.run:91 - Interrupted!!! .418 is showing up before .415 Please see my filter below for ALWAYS if that even remotely has anything to do with this. <turboFilter class="ch.qos.logback.classic.turbo.MarkerFilter"> <Name>AlwaysTurboFilter</Name> <Marker>ALWAYS</Marker> <OnMatch>ACCEPT</OnMatch> </turboFilter> It happens to both STDOUT and my log file in the same order. Subsequent runs haven't show this and it is happening during shutdown so I am not really that concerned about it, but I figured I would report and see if there's an explanation for it. Here is my jar information.. slf4j-api-1.6.6.jar logback-classic-1.0.6.jar logback-core-1.0.6.jar Thanks, Dave

2 1