October 2008 - logback-user

RollingFileAppender
by Greg Flex 29 Oct '08

29 Oct '08

Hi All, Could someone please post a simple example on how to use the RollingFileAppender programmatically? I'm having problems figuring this out. (and massages such as: No context given.... etc.) Basically what I'd like to do is set everything in my java program. Write to a file but adding stuff like computer's IP address and its name etc. Most importantly, I'd like to modify the file name itself. Say in the format: IP_address_date {yyyy-MM-dd_HH-mm-ss}.log Thanks a lot, Greg.

2 6

Release of version 0.9.11
by Ceki Gulcu 28 Oct '08

28 Oct '08

28th of October 2008 - Release of version 0.9.11 Version 0.9.11 is a maintenance release fixing a crude bug introduced in logback version 0.9.10. Fixed LBCLASSIC-77 reported independenly by Gianni Doe, Yannick Haudry and Yossi Shaul. The childValue() method of CopyOnInheritThreadLocal class part of MDC code no longer throws a NullPointerException. 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 logback announce mailing list. To subscribe to logback-announce list, please visit the following URL. http://qos.ch/mailman/listinfo/logback-announce Enjoy, -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

2 3

Release of logback version 0.9.10
by Ceki Gulcu 28 Oct '08

28 Oct '08

27th of October 2008 - Release of version 0.9.10 After a lull of 7 months, I am happy to announce the release of logback version 0.9.10. This version includes both bug fixes as well as significant enhancements. Here is the list: In case of errors during initialization, logback-classic now automatically prints out its internal status. This has been a frequently requested feature. The LogbackValve in logback-access (ensuring integration with Tomcat), will now systematically print its internal status upon initialization, unless told to be quiet. This greatly helps troubleshooting the configration of logback-access under Tomcat. Fixed bug 147 which occured when the user inadvertently attempted to set the layout of a SyslogAppender. The code now actively prevents this. Documenation has been updated to reflect the change. Fixed bug LBCLASSIC-56 originally reported by Michel Colette. Backslash characters are now correctly interpreted in filename patterns. The TurboFilterChain in a LoggerContext is now cleared when the shutdownAndReset method is called. This problem was reported on May 1st, 2008, by Julia Hu on the logback developpers list. Fixed issue LBCORE-48. During rollover, compression of large files would bring all logging to a halt. In this latest release, the rolled over file is first renamed, which is a relatively fast operation, and only then is the renamed file compressed asyncronously (in a separate thread). Fixed issue LBCORE-11. It is now possible to instruct TimeBasedRollingPolicy to delete old files, thus controlling then number of archived log files. Fixed issue LBCORE-42. If the parent directory of the log file does not exist, then FileAppender will create it, including any necessary but nonexistent parent directories. Fixed LBCORE-15 reported by Klaus Unger and others. DBAppender should now work with Oracle 9, 10g and 11g, regardless of the JDBC driver type used. Fixed issue LBCORE-17 reported by Thorbjørn Ravn Andersen. Logback now relies on Geronimo JMS API specifications instead of Sun's JMS API specification, the latter requiring manual installation. With Geronimo JMS, logback can be built using Maven without needing to manually install any dependencies. Fixed issue LBCORE-23. In PatternLayout, parenthesis can be used to group conversion patterns. It follows that the '(' and ')' carry special meaning and need to be escaped to be used as literals. This is now properly documented. The location of the default configuration file can be specified by a system property. This feature was requested in LBCORE-32 by Ted Graham, Matt Fowles, Ivan Biddles and Ralph Goers. Fixed issue LBCORE-55 reported by Natan Cox. WriterAppender now outputs its presentation footer and file footer in the the correct order. Fixed issue LBCORE-27 reported by Peter Royal. SMTPAppender now outputs its presentation footer and file footer in the the correct order. Fixed issue LBCLASSIC-67 reported by Alessandro Fustini. SMTPAppender now correctly configures the layout used to format the subject line of the outgoing email. It no longer appends a lengthy stack trace to the subject line. Fixed issue LBCLASSIC-68 reported by Gili Tzabari. In environments where the TCCL (Thread Context Class Laoder) was not set, logback was unable to located its default configuraiton files. Logback now uses the class loader that loaded logback itself to locate its resources instead of the TCCL. This approach is simpler and deemed to cover more environments, i.e. more widely applicable. Fixed issue LBGENERAL-24 reported by Hung Tang. SMTPAppender now supports plain username/password authentication as well as both the STARTTLS command and SSL connections. Fixed issue LBCLASSIC-48 reported by Peter Royal. SyslogAppender now correctly outputs hours as 0-23 and not as 1-12 as previously. Added a new TurboFilter called DynamicThresholdFilter which can filter events depending on MDC values based on a variery of criteria such as company name, product or the end user. This filter was contributed by Ralph Goers in LBCLASSIC-53. 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 logback announce mailing list. To subscribe to logback-announce list, please visit the following URL. http://qos.ch/mailman/listinfo/logback-announce Enjoy, -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

4 4

jul-to-slf4j conflicts with logback-classic
by cowwoc 24 Oct '08

24 Oct '08

Hi, If I deploy: slf4j-api logback-classic logback-core jul-to-slf4j I get: Deploying application in domain failed; Logging factory implementation cannot be null. See also http://www.slf4j.org/codes.html#null_LF but if I remove jul-to-slf4j from the classpath it works just fine (except, obviously, jul-to-slf4j is disabled). I am invoking SLF4JBridgeHandler.install() from within a ServletContextListener. Perhaps this is too late somehow? What am I doing wrong? Thank you, Gili -- View this message in context: http://www.nabble.com/jul-to-slf4j-conflicts-with-logback-classic-tp1959092… Sent from the Logback User mailing list archive at Nabble.com.

3 9

SMTPAppender with level WARN?
by Joop Vriend 21 Oct '08

21 Oct '08

Hi, I'm trying to configure logback with an SMTPAppender that mails *every* log message of level WARN or higher, but I can't get it working. I've tried to use a (Threshold)filter, but that didn't work. (Why can't you just use filters with SMTPAppender?!?) I've tried to use an EvaluatorFilter with an expression 'level >= WARN', but that didn't work either. Now I'm trying to use a custom evaluator, but still can't get it working... :-( Level ERROR is being e-mailed, but other levels not. For testing purposes I (even) wrote a custom evaluator-class that always returns 'true' in it's evaluate()-method: public class AlwaysTrueEvaluator extends ContextAwareBase implements EventEvaluator { String name; boolean started; public boolean evaluate(Object event) throws NullPointerException, EvaluationException { return true; } public void setName(String name) { this.name = name; } public String getName() { return name; } public boolean isStarted() { return started; } public void start() { started = true; } public void stop() { started = false; } } This is my logback.xml file: <configuration> <appender name="RootFileAppender" class="ch.qos.logback.core.rolling.RollingFileAppender"> <append>true</append> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>debug</level> </filter> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${catalina.base}/logs/logback-root.%d{yyyy-MM-dd}.log.gz</fileNamePattern> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%date{yyyy-MM-dd HH:mm:ss} %class %method $%file:%line$%n %level: %message%n</pattern> </layout> </appender> <appender name="RootEmailAppender" class="ch.qos.logback.classic.net.SMTPAppender"> <bufferSize>1</bufferSize> <SMTPHost>_SMTP_HOST_</SMTPHost> <to>_TO_ADDRESS_</to> <from>_FROM_ADDRESS_</from> <subject>logback logrecord</subject> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%date{yyyy-MM-dd HH:mm:ss} %class %method $%file:%line$%n %level: %message%n</pattern> </layout> <evaluator class="packagename.AlwaysTrueEvaluator"/> </appender> <root> <level value ="debug"/> <appender-ref ref="RootFileAppender"/> <appender-ref ref="RootEmailAppender"/> </root> </configuration> I'm using logback 0.9.9 with slf4j 1.5.5 on Tomcat 6.0. Any help is greatly appreciated! Kind regards, Joop Vriend.

3 4

Mismatch error version from 1.5.4
by alex 21 Oct '08

21 Oct '08

Hi, I upgraded SLF4J to 1.5.3 to 1.5.4 and a message appears when launch my program : SLF4J: The version of your slf4j-binding is probably older than 1.5.4, and differs from 1.5.4, the expected version. SLF4J: See http://www.slf4j.org/codes.html#version_mismatch for further details. I red version_mismatch error but I do not found error in my configuration. I tried to unzip again the lib 1.5.4 and check the files and it seems all ok. This is the poperties from Eclipse launch with 1.5.4 C:\jdk160\bin\javaw.exe -Xmx512M -classpath C:\dnsvmware25\testvmware;D:\install\libExplode\axis1-4\wsdl4j-1.5.1.jar;D:\install\libExplode\axis1-4\activation.jar;D:\install\libExplode\axis1-4\jaxen-core.jar;D:\install\libExplode\axis1-4\jaxen-jdom.jar;D:\install\libExplode\axis1-4\jdom.jar;D:\install\libExplode\axis1-4\mailapi.jar;D:\install\libExplode\axis1-4\saxpath.jar;D:\install\libExplode\axis1-4\smtp.jar;D:\install\libExplode\axis1-4\wbem.jar;D:\install\libExplode\axis1-4\xalan.jar;D:\install\libExplode\axis1-4\xerces.jar;D:\install\libExplode\axis1-4\xml-apis.jar;D:\install\libExplode\axis1-4\axis.jar;D:\install\libExplode\axis1-4\axis-ant.jar;D:\install\libExplode\axis1-4\commons-discovery-0.2.jar;D:\install\libExplode\axis1-4\jaxrpc.jar;D:\install\libExplode\axis1-4\saaj.jar;D:\install\libExplode\logback\logback-access-0.9.9.jar;D:\install\libExplode\logback\logback-classic-0.9.9.jar;D:\install\libExplode\logback\logback-core-0.9.9.jar;D:\install\libExplode\logback\janino2_5_15.jar;D:\install\libExplode\vmware25\vim25.jar;D:\install\libExplode\vmware25\vim.jar;D:\install\libExplode\slf4j_154\jul-to-slf4j-1.5.4.jar;D:\install\libExplode\slf4j_154\log4j-over-slf4j-1.5.4.jar;D:\install\libExplode\slf4j_154\slf4j-api-1.5.4.jar;D:\install\libExplode\slf4j_154\jcl-over-slf4j-1.5.4.jar -agentlib:jdwp=transport=dt_socket,suspend=y,address=localhost:3903 test.ListPort This is the poperties from Eclipse launch with 1.5.3 C:\jdk160\bin\javaw.exe -Xmx512M -classpath C:\dnsvmware25\testvmware;D:\install\libExplode\axis1-4\wsdl4j-1.5.1.jar;D:\install\libExplode\axis1-4\activation.jar;D:\install\libExplode\axis1-4\jaxen-core.jar;D:\install\libExplode\axis1-4\jaxen-jdom.jar;D:\install\libExplode\axis1-4\jdom.jar;D:\install\libExplode\axis1-4\mailapi.jar;D:\install\libExplode\axis1-4\saxpath.jar;D:\install\libExplode\axis1-4\smtp.jar;D:\install\libExplode\axis1-4\wbem.jar;D:\install\libExplode\axis1-4\xalan.jar;D:\install\libExplode\axis1-4\xerces.jar;D:\install\libExplode\axis1-4\xml-apis.jar;D:\install\libExplode\axis1-4\axis.jar;D:\install\libExplode\axis1-4\axis-ant.jar;D:\install\libExplode\axis1-4\commons-discovery-0.2.jar;D:\install\libExplode\axis1-4\jaxrpc.jar;D:\install\libExplode\axis1-4\saaj.jar;D:\install\libExplode\logback\logback-access-0.9.9.jar;D:\install\libExplode\logback\logback-classic-0.9.9.jar;D:\install\libExplode\logback\logback-core-0.9.9.jar;D:\install\libExplode\logback\janino2_5_15.jar;D:\install\libExplode\vmware25\vim25.jar;D:\install\libExplode\vmware25\vim.jar;D:\install\libExplode\slf4j_153\slf4j-api-1.5.3.jar;D:\install\libExplode\slf4j_153\jcl-over-slf4j-1.5.3.jar;D:\install\libExplode\slf4j_153\jul-to-slf4j-1.5.3.jar;D:\install\libExplode\slf4j_153\log4j-over-slf4j-1.5.3.jar -agentlib:jdwp=transport=dt_socket,suspend=y,address=localhost:3891 test.ListPort Any Hint ? Thanks a lot for all

3 5

Configure at runtime
by Michael 20 Oct '08

20 Oct '08

Hi, I've been searching in the docs and the mailinglist but it seems like Logback does not support a reconfiguration every x seconds like log4j's DOMConfigurator. Is this feature planned? Thanks, Mike -- <NO> OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org

4 23

Dumping a CyclicBuffer
by mweeda 15 Oct '08

15 Oct '08

Hi, Objective: Dump a "history" of recent program operations to a log file when an Exception arises. By logging to a CyclicBufferAppender, a recent history at a fairly granular level (INFO, or possibly DEBUG) can be maintained without accumulating massive amounts of data, and with a minimum of overhead. Setting this up to log to the Cyclical Buffer went well. To get the data out of the CyclicBuffer and log it to a file, a reference to the CyclicBufferAppender object is needed, and it is not clear how to get one. It seems like log.getAppender(String name) should return an Appender, but it doesn't. How can I obtain such a reference? Also, once a reference is obtained, and an Object is returned from cyclicBufferAppender.get(i), what class will that object be? I'm hoping it is a LoggingEvent object, in which case a simple call to the fileAppender.doAppend method with the event as a parameter will log the event to a "permanent" log. Again, the code will need to obtain a reference to the appropriate FileAppender to log it to. (Appropriate might be hardcoded, or specified in a properties file.) Most of the configuration is being done in logback.xml. (File is attached.) Program code, other than wanting to dump the MEMORY appender, is limited to: static final Logger log = LoggerFactory.getLogger(Main.class); and various log.X method calls. As an aside, it would be even better to loop over all Appenders, and check to see which ones are CyclicBufferAppenders. The code would dump then contents of all of the CyclicBufferAppenders, or selected ones based on some user options. Thanks in advance for your insight. Mike

2 4

Logback eclipse plugin enhancments
by Алексей Кузнецов 14 Oct '08

14 Oct '08

Hello! I'm playing with logback and its eclipse plugin (ch.qos.logback.eclipse_1.1.0.zip) and for me it miss 2 features: 1) In "Logback View Filters" window it would be more user frendly to use comboboxes for slecting "Action on match" and "Action on mismatch" instead of text fields. 2) In "Logback View Filters" window it would be really useful to add column "Active"(or "Use" or smth. like that) in table with expressions to activate/deactivate some filters without deleting them. Alexey Kuznetsov kuaw26(a)mail.ru

3 3

Re: [logback-user] TimeBasedRollingPolicy
by Gam 14 Oct '08

14 Oct '08

On 12 Oct 2008, at 21:40, logback-user-request(a)qos.ch wrote: > thanx for your response. my test-application ran under a minute. > and now it's clear to me that every time > i restart the application the logging-configuration starts from > scratch. therefore i never had a rollover. > I introduced a sleep to make my app run longer than a minute; and > it works. thanks for your help. I discovered the same. I've been using log4j for years and it behaves differently than logback in this context, it will roll the log according to the configuration regardless of the execution context, which is imho a better behavior. I hope it would be possible to fix this issue or at least give an option between the two behaviors. Here is how I use it: - I have a monitoring task that is run every ten minutes and lasts for a dozen of seconds. I set logback to roll the logs everyday but it never happens because logback rolls ONLY if it is running while the date changes. I end up with a very huge log file that never rolls. Log4j will roll it during the first new execution after the date has changed. What do you think? Best Regards, Gam.

2 1