December 2010 - logback-user

Confused about jul-to-slf4j bridge and LevelChangePropagator
by Kristof Pelckmans 30 Dec '10

30 Dec '10

Hi, Think I set up the SLF4JBridgeHandler and LevelChangePropagator correctly, since I am now getting all log messages via SLF4J and changes in the level of my root logger are propagated to JUL but I cannot seem to tweak the levels of my JUL loggers: My configuration file <configuration> <contextListener class="ch.qos.logback.classic.jul.LevelChangePropagator"> <resetJUL>true</resetJUL> </contextListener> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern> </encoder> </appender> <logger name="com.google.inject" level="debug" /> <root level="info"> <appender-ref ref="STDOUT" /> </root> </configuration> and debug output 23:28:35,723 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy] 23:28:35,723 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml] 23:28:35,723 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/.../war/WEB-INF/classes/logback.xml] 23:28:35,763 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set 23:28:35,764 |-INFO in ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Adding LoggerContextListener of type [ch.qos.logback.classic.jul.LevelChangePropagator] to the object stack 23:28:35,778 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@118cb3a - Propagating DEBUG level on Logger[ROOT] onto the JUL framework 23:28:35,778 |-INFO in ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Starting LoggerContextListener 23:28:35,778 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 23:28:35,781 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT] 23:28:35,787 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 23:28:35,826 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.google.inject] to DEBUG 23:28:35,826 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@118cb3a - Propagating DEBUG level on Logger[com.google.inject] onto the JUL framework 23:28:35,826 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO 23:28:35,826 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@118cb3a - Propagating INFO level on Logger[ROOT] onto the JUL framework 23:28:35,826 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT] Although it states "Propagating DEBUG level on Logger[com.google.inject] onto the JUL framework", it does not seem to work. Moreover, if I manually do java.util.logging.Logger logger = java.util.logging.Logger.getLogger("com.google.inject"); logger.setLevel(java.util.logging.Level.FINEST); I do get debug messages! What am I doing wrong? Many thanks, Kristof

1 0

Multiple MDC variable substitution
by cdub23 30 Dec '10

30 Dec '10

Hi, I have been trying to pass multiple values in the MDC. I want to use the values to create unique paths and log file names. I'm unable to use more than one value that is passed to the MDC. How would I go about doing this? I have also tried using SiftingAppender but I was not able figure out how to use more than one discriminator. Is there a way to store the value from the pattern %X{VAR}? Thanks MDC.put("jobName", jobName); MDC.put("station", station); //logback.groovy file import ch.qos.logback.classic.encoder.PatternLayoutEncoder import ch.qos.logback.classic.PatternLayout import ch.qos.logback.classic.sift.GSiftingAppender import ch.qos.logback.classic.sift.MDCBasedDiscriminator import ch.qos.logback.core.ConsoleAppender import ch.qos.logback.core.FileAppender import ch.qos.logback.core.rolling.FixedWindowRollingPolicy import ch.qos.logback.core.rolling.RollingFileAppender import ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy import ch.qos.logback.core.spi.LifeCycle import static ch.qos.logback.classic.Level.DEBUG import static ch.qos.logback.classic.Level.INFO import static ch.qos.logback.classic.Level.OFF appender("FILE", FileAppender) { file = "logs/${station}/${jobName}.log append = true encoder( PatternLayoutEncoder ) { pattern = "[%date] %-5level: %msg [%file:%line] %n" } } //Only 1 VAR will contain a value. appender("SIFT", GSiftingAppender) { discriminator(MDCBasedDiscriminator) { key = "jobName" defaultValue = "unknown" } discriminator(MDCBasedDiscriminator) { key = "station" defaultValue = "unknown" } sift { appender("FILE-${jobName}", FileAppender) { file = "logs/${station}/${jobName}.log" append = false layout(PatternLayout) { pattern = "%d [%thread] %level %mdc %logger{35} - %msg%n" } } } } -- View this message in context: http://old.nabble.com/Multiple-MDC-variable-substitution-tp30560208p3056020… Sent from the Logback User mailing list archive at Nabble.com.

1 0

User manual in logback version 0.9.27
by Merritt H Derr 29 Dec '10

29 Dec '10

I just tooked at the user manual for version 0.9.27 to refresh myself on a couple of details related to the JMSQueueAppender and find that it is missing from the manual for this version of logback. Is this intentional or an oversight. This information was in the 0.9.26 manual. Merritt Derr Join us on Facebook at www.facebook.com/NYCMInsurance. ***CONFIDENTIALITY NOTICE*** This email and any attachments to it are confidential and intended solely for the individual or entity to whom it is addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you have received this email in error, please contact the sender by reply email and destroy all copies of the original message.

3 3

Release of logback v0.9.27
by Ceki Gülcü 22 Dec '10

22 Dec '10

Hello all, I am happy to announce the release of logback version 0.9.27. Please refer to the news page for precise details. http://logback.qos.ch/news.html You can download logback, including full source code, class files and documentation on our download page, shown below. http://logback.qos.ch/download.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce Enjoy, -- Ceki

1 0

AND in if condition ?
by Ed Bras 20 Dec '10

20 Dec '10

I want to do something like this in my logback.xml configuration: <if condition='!property("app.environment").equals("dev") && !property("app.environment").equals("build")'> <then> ... But that doesn't work. How to define a "AND" in a if condition? Here can I find more examples about this syntax? Ed

2 2

SMTPAppender
by Ed Bras 20 Dec '10

20 Dec '10

If an error occurs during sending in the SMTPAppender, it adds a status. How can I see these status messages such that I see the details of the sending exception? I would like these status messages to appear in my stdout or log file.. Regards, Ed

2 2

Variable substitution using a separate file with groovy configuration
by Muyen Lee 20 Dec '10

20 Dec '10

Hi, How do I use variable substitution using a separate file with groovy configuration? I tried xml to groovy translate tool but I got an error message // File attribute not supported for <property> element <configuration> <property file="src/main/java/chapters/configuration/variables1.properties" /> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <file>${USER_HOME}/myApp.log</file> <encoder> <pattern>%msg%n</pattern> </encoder> </appender> <root level="debug"> <appender-ref ref="FILE" /> </root> </configuration> Regards, Arsene

2 1

Appender with a triggering level
by Bee-lindgren, Bert A 20 Dec '10

20 Dec '10

This email is about a method to save detailed log output from failed operations but not from successful operations. Our programs try to put all pertinent information in MDC properties or in an error message itself, but sometimes we have found it helpful to have the debug/info message to show what led up to an error. Therefore, we keep debug/info logs when we don't need 99.99% of it; we only need it in the rare occurrence of an error. We already have the concept of a thread-specific appender that processes Events for a single thread (fwiw, we use this to capture server-side messages for client requests and then send them back to the client). What do people think about this idea: 1. An appender with two levels: BaseLevel and TriggerLevel (this would probably be a subclass of AppenderBase and call super(layout, BaseLevel) 2. Appender's append() method stores (List, CircularBuffer, etc) ILoggingEvents >= BaseLevel 3. If an event happens >=TriggerLevel, Appender prints all stored events as well as all future events Thanks for your feedback, Bert Bee-Lindgren

3 2

Log rotation & .tmp droppings
by Bee-lindgren, Bert A 17 Dec '10

17 Dec '10

We are seeing logback leave .tmp files behind in the log directory, presumably due to a hiccup during log rotation or gzip. Size 2365956 Dec 11 00:00 statsreceiver.log.2010-12-10.gz 2679618 Dec 12 00:01 statsreceiver.log.2010-12-11.gz 9190879942 Dec 12 04:00 statsreceiver-debug.log23124507802228260.tmp 2542799 Dec 13 00:00 statsreceiver.log.2010-12-12.gz 9137740366 Dec 13 04:00 statsreceiver-debug.log23210907242250260.tmp 543937393 Dec 13 20:07 statsreceiver-debug.log.2010-12-13_19:00.gz 548781049 Dec 13 22:07 statsreceiver-debug.log.2010-12-13_21:00.gz 2284216 Dec 14 00:00 statsreceiver.log.2010-12-13.gz 8127562 Dec 15 00:00 statsreceiver.log.2010-12-14.gz 19067117496 Dec 15 13:00 statsreceiver-debug.log23416102512001260.tmp 18177324477 Dec 15 16:00 statsreceiver-debug.log23426920509229260.tmp 2257423 Dec 15 23:00 statsreceiver-debug.log.2010-12-15_22:00.gz The logback jar versions are: WEB-INF/lib/logback-classic-0.9.26.jar WEB-INF/lib/logback-core-0.9.26.jar There is only a single application writing to those files, though it is conceivable that the .tmp droppings correlate to restarts of that application. If this is expected on application restarts, then could logback start gzip'ing them again when it comes back? Here is the logback.xml file: <?xml version="1.0" encoding="UTF-8"?> <configuration scan="true" scanPeriod="60 seconds"> <appender name="FILE_WARN" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${logdir:-.}/${prog:-unknown}.log</file> <append>true</append> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>warn</level> </filter> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${logdir:-.}/${prog:-unknown}.log.%d{yyyy-MM-dd}.gz</fileNamePattern> <maxHistory>7</maxHistory> </rollingPolicy> <encoder> <pattern>%-30(%d{yyyy-MM-dd HH:mm:ss} %.-1level :) %m Context:[%X{GTNDC_INFO}]%n</pattern> </encoder> </appender> <appender name="FILE_DEBUG" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${logdir:-.}/${prog:-unknown}-debug.log</file> <append>true</append> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>debug</level> </filter> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${logdir:-.}/${prog:-unknown}-debug.log.%d{yyyy-MM-dd_HH:00}.gz</fileNamePattern> <maxHistory>36</maxHistory> </rollingPolicy> <encoder> <pattern>%-60(%d{yyyy-MM-dd HH:mm:ss} [%thread] %.-1level :) %m Context:[%X{GTNDC_INFO}]%n</pattern> </encoder> </appender> <logger name="org.apache.directory" level="WARN"/> <root><level value="debug"/> <appender-ref ref="FILE_WARN"/> <appender-ref ref="FILE_DEBUG"/> </root> </configuration>

2 2

NullPointerException on info
by Guy Korland 14 Dec '10

14 Dec '10

Any ideas? java.lang.NullPointerException at ch.qos.logback.classic.Logger.filterAndLog_1(Logger.java:426) at ch.qos.logback.classic.Logger.info(Logger.java:627) Guy

2 1