March 2007 - logback-user - mailman3.qos.ch

An OSGi bundle for logback?
by John E. Conlon 14 Sep '07

14 Sep '07

Are there any plans for a logback OSGi bundle in the foreseeable future? ;-)

3 3

Using logback in tomcat
by Michael Abato 17 Apr '07

17 Apr '07

I'm successfully using logback with Tomcat and have a small suggestion that will help people with complex deployments: look for logback-access.xml in system property catalina.base rather than catalina.home. Tomcat is intentionally setup such that multiple instances (java VMs) can be running off the same copy of the tomcat distribution and set up private CATALINA_BASE directories for server config, logs, temp space, etc. Such setups will naturally want to configure logback in CATALINA_BASE, not in the (potentially read-only) CATALINA_HOME. In cases where the user does *not* set CATALINA_BASE, it takes the same value as CATALINA_HOME (which is generally the same as TOMCAT_HOME). I've patched the source of LogbackValve.java to do this and it works well. The change of "catalina.home" to "catalina.base" is to trivial for a formal patch... On a related note, I've also configured tomcat to use log4j/logback for internal logging, which also works quite well. I noticed in a previous post you "don't recommend this at this time" and would like to know the reason(s). Routing *all* logging through one logger/one config, which in turn can separate "live" logs from rotated out "archive" logs in a separate directory is a godsend. I'm assuming it is because doing this requires mucking around with the tomcat startup scripts to replace ACL from the very beginning of the tomcat boot process. I'd already created a "boot" directory with a dynamic set of jar's and classes (for unrelated reasons) so switching ACL to log4j/logback was pretty trivial for me. Is there more to the reluctance than the fact that there is no "drop in" way to do it? If there's interest, I can tidy up my tomcat patch and post the details. -- View this message in context: http://www.nabble.com/Using-logback-in-tomcat-tf2890321.html#a8074672 Sent from the Logback User mailing list archive at Nabble.com.

2 2

shutting off logger
by Alexandre Jaquet 02 Apr '07

02 Apr '07

Hi, I would like to know, how to shutting off the logger, I thinked I only needed to set <configuration debug="false"> but as I see that's not enough. Any advice would be appreciate. Thanks. Alexandre

2 2

[ANN] Logback Console Plugin 1.0.1 released
by Sebastien Pennec 30 Mar '07

30 Mar '07

Hello, Just a quick note to tell everyone who downloaded the Console Plugin for Eclipse yesterday or today that a new version, 1.0.1, has just come out. It corrects a small bug which prevented the display of stack traces in a specific situation. You can download the new version on our download page[1]. Enjoy :) Sébastien [1]http://logback.qos.ch/download.html -- Sébastien Pennec sebastien(a)qos.ch Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch/

1 0

[ANN] Release of logback 0.9.4
by Sebastien Pennec 30 Mar '07

30 Mar '07

March 29th, 2007 - Release of version 0.9.4 Significant bug fixes made to c.q.l.access.TeeFilter and Co. Images and other binary files are now intercepted and replayed correctly. As for "x-www-form-urlencoded" post requests, their input buffer is left untouched. In a best-effort attempt, the input buffer for "x-www-form-urlencoded" post requests is later reconstructed through the request parameters. However, it may differ from the original buffer. The logback team released today the first version of a plugin for Eclipse that allows developpers to see the logs generated by a running application. It offers several great features, check the user guide[1] for more information. [1]http://logback.qos.ch/consolePlugin.html -- Sébastien Pennec sebastien(a)qos.ch Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch/

2 3

Daily rolling appender
by Keith 30 Mar '07

30 Mar '07

I am looking to use RollingFileAppender and TimeBasedRollingPolicy to implement my solution of rotating logs and compressing them each day. The configuration looks something like that: <configuration> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>logFile.log</File> *<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>logFile.%d{yyyy-MM-dd}.log</FileNamePattern> </rollingPolicy>* <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%-4relative [%thread] %-5level %logger{35} - %msg%n</Pattern> </layout> </appender> <root> <level value="debug" /> <appender-ref ref="FILE" /> </root> </configuration> However, I would only like to keep seven compressed daily logs only. How do I specify such an option in configuration file? Will I be able to use MaxIndex and MinIndex? Thanks Keith

2 1

[ANN] Release of logback 0.9.3
by Sebastien Pennec 21 Mar '07

21 Mar '07

March 20th, 2007 - Release of version 0.9.3 Includes in configuration files are now supported by Joran, logback's configuration framework. A file can contain an include element that has a file or url attribute pointing to a configuration file. See the chapter about configuration[1] in the logback's online manual for more information. Corrected bug 53 reported by Wilkins Poe. There is now a dependencies page[2] that shows the requirements of each of logback's modules. After a discussion on the SLF4J mailing list[3] started by Franck Routier, a correction has been made when logging using the JCL104-over-slf4j module. Logback now correctly shows the caller location information. As with most of the logback releases, the documentation has been improved in many aspects. [1]http://logback.qos.ch/manual/joran.html#Include [2]http://logback.qos.ch/dependencies.html [3]http://www.slf4j.org/pipermail/user/2007-March/000297.html -- Sébastien Pennec sebastien(a)qos.ch Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch/

3 3

AsyncAppender?
by Anders Wallgren 19 Mar '07

19 Mar '07

Are there plans to provide AsyncAppender-like functionality? Perhaps I'm just not looking in the right place? anders -- View this message in context: http://www.nabble.com/AsyncAppender--tf3394214.html#a9449224 Sent from the Logback User mailing list archive at Nabble.com.

3 5

Logback configuration
by Hausherr, Jens 15 Mar '07

15 Mar '07

Hi, lgoback seems to solve some problems that log4j has, but I did not yet find the answer to my most pressign question: Does logback handle multiple configurations in a controllable manner? The crucial problem with log4j was its great propularity not only with application developers but also with library developers that sometimes packed an log4j confguration file into their jars. So in almost every project it could happen that one did configure log4j and only get strange or even no output because ther is some other log4j configration overriding the one intended by oneself. If logback improves this behavior of log4j I'd be switching immediately with flying colors! Regards, jens This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

5 8

logback performance clarification
by mandeep singh 14 Mar '07

14 Mar '07

Hi, I I am a new user of logback and would like to use it in my project. Currently we are using log4j, but we have very strict performance requirements and it would be gr8 if logback performs better then log4j. I did some preliminary tests to compare the performace of the two ..and i observed that at some places logback is certainly better , but i also observed a behaviour which is contrary to what is described in the documentation. I am attaching the source code and my config files for the test . The queries I have are as following - 1. The documentation says that the "logbacklogger.debug("SEE IF THIS IS LOGGED {}.", i);" is faster then if (logbacklogger.isDebugEnabled()) logbacklogger.debug("SEE IF THIS IS LOGGED " + i + "."); but i observed that this is only true if the logging is configured for debug . For any other logging level the second approach is still more performant. This means that in a production env I must still have the check for isDebugEnabled. Is that intended or am i missing something. 2. Something very strange that i observed in my test was that if i run my outer loop 10 times then always at the 7th invocation the logback took much longer time. I was able to get this behaviour consistently. Anyways for the time being I am attaching my source code and the config files below ...maybe somebody can point out the errors or way of improvement. ########################################JAVA FILE################################################## package mandy.test.programs; import org.slf4j.Logger; import org.slf4j.LoggerFactory; public class Logtester { static Logger logbacklogger = LoggerFactory.getLogger(Logtester.class); static org.apache.log4j.Logger log4jlogger = org.apache.log4j.Logger.getLogger(Logtester.class); public static void main(String[] args) throws InterruptedException { for (int j = 0; j < 5; j++ ) { System.out.println("#######################################"); System.out.println("TEST NUMBER "+j); System.out.println("#######################################"); long start = System.nanoTime(); for (int i = 0; i < 500; i++ ) { log4jlogger.debug("SEE IF THIS IS LOGGED " + i + "."); } System.out.println("time taken in nanoseconds in first log4j test is " + (System.nanoTime() - start)); start = System.nanoTime(); for (int i = 0; i < 500; i++ ) { if (log4jlogger.isDebugEnabled()) log4jlogger.debug("SEE IF THIS IS LOGGED " + i + "."); } System.out.println("time taken in nanoseconds in second log4j test is " + (System.nanoTime() - start)); Thread.sleep(1000); start = System.nanoTime(); for (int i = 0; i < 500; i++ ) { logbacklogger.debug("SEE IF THIS IS LOGGED " + i + "."); } System.out.println("time taken in nanoseconds in first logback test is " + (System.nanoTime() - start)); start = System.nanoTime(); for (int i = 0; i < 500; i++ ) { if (logbacklogger.isDebugEnabled()) logbacklogger.debug("SEE IF THIS IS LOGGED " + i + "."); } System.out.println("time taken in nanoseconds in second logback test is " + (System.nanoTime() - start)); Thread.sleep(1000); start = System.nanoTime(); for (int i = 0; i < 500; i++ ) { logbacklogger.debug("SEE IF THIS IS LOGGED {}.", i); } System.out.println("time taken in nanoseconds in third logback test is " + (System.nanoTime() - start)); } } } ###################################################LOG4J CONFIG###################################### <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE log4j:configuration SYSTEM "../resource/log4j.dtd"> <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="false"> <appender name="TestLogfile" class=" org.apache.log4j.RollingFileAppender"> <param name="File" value="d:/mandy/Test_Programs/testlog4j.log"/> <param name="MaxFileSize" value="1000KB"/> <param name="maxBackupIndex" value="1"/> <param name="Append" value="true"/> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="%d{ISO8601} %5p [%t] %c{1} %X{transactionId} - %m%n"/> </layout> </appender> <logger name="mandy.test.programs" additivity="false"> <level value="debug"/> <appender-ref ref="TestLogfile"/> </logger> </log4j:configuration> #############################################LOGBACK CONFIG############################################ <configuration> <appender name="TestLogfile" class="ch.qos.logback.core.FileAppender"> <File>d:/mandy/Test_Programs/testlogback.log</File> <Append>false</Append> <Encoding>UTF-8</Encoding> <BufferedIO>true</BufferedIO> <ImmediateFlush>true</ImmediateFlush> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%-4relative [%thread] %-5level %logger{35} - %msg%n</Pattern> </layout> </appender> <root> <level value="debug" /> <appender-ref ref="TestLogfile" /> </root> </configuration> #########################################OUTPUT WITH LOG LEVEL SET TO INFO IN BOTH CONFIG FILES ############################ ####################################### TEST NUMBER 0 ####################################### time taken in nanoseconds in first log4j test is 1287035 time taken in nanoseconds in second log4j test is 425473 time taken in nanoseconds in first logback test is 1988521 time taken in nanoseconds in second logback test is 60622 time taken in nanoseconds in third logback test is 1378387 ####################################### TEST NUMBER 1 ####################################### time taken in nanoseconds in first log4j test is 2332139 time taken in nanoseconds in second log4j test is 115378 time taken in nanoseconds in first logback test is 1550756 time taken in nanoseconds in second logback test is 50565 time taken in nanoseconds in third logback test is 374069 ####################################### TEST NUMBER 2 ####################################### time taken in nanoseconds in first log4j test is 2050540 time taken in nanoseconds in second log4j test is 670755 time taken in nanoseconds in first logback test is 846756 time taken in nanoseconds in second logback test is 415974 time taken in nanoseconds in third logback test is 1142044 ####################################### TEST NUMBER 3 ####################################### time taken in nanoseconds in first log4j test is 321828 time taken in nanoseconds in second log4j test is 43581 time taken in nanoseconds in first logback test is 358985 time taken in nanoseconds in second logback test is 51962 time taken in nanoseconds in third logback test is 127390 ####################################### TEST NUMBER 4 ####################################### time taken in nanoseconds in first log4j test is 323784 time taken in nanoseconds in second log4j test is 43581 time taken in nanoseconds in first logback test is 362337 time taken in nanoseconds in second logback test is 45816 time taken in nanoseconds in third logback test is 124597 ####################################### TEST NUMBER 5 ####################################### time taken in nanoseconds in first log4j test is 326578 time taken in nanoseconds in second log4j test is 43581 time taken in nanoseconds in first logback test is 5767493 time taken in nanoseconds in second logback test is 25981 time taken in nanoseconds in third logback test is 103365 ####################################### TEST NUMBER 6 ####################################### time taken in nanoseconds in first log4j test is 261206 time taken in nanoseconds in second log4j test is 28775 time taken in nanoseconds in first logback test is 239416 time taken in nanoseconds in second logback test is 5867 time taken in nanoseconds in third logback test is 59505 ####################################### TEST NUMBER 7 ####################################### time taken in nanoseconds in first log4j test is 223492 time taken in nanoseconds in second log4j test is 12851 time taken in nanoseconds in first logback test is 235784 time taken in nanoseconds in second logback test is 5867 time taken in nanoseconds in third logback test is 58667 ####################################### TEST NUMBER 8 ####################################### time taken in nanoseconds in first log4j test is 220977 time taken in nanoseconds in second log4j test is 12851 time taken in nanoseconds in first logback test is 238299 time taken in nanoseconds in second logback test is 5867 time taken in nanoseconds in third logback test is 61460 ####################################### TEST NUMBER 9 ####################################### time taken in nanoseconds in first log4j test is 223212 time taken in nanoseconds in second log4j test is 12851 time taken in nanoseconds in first logback test is 237461 time taken in nanoseconds in second logback test is 5308 time taken in nanoseconds in third logback test is 62019 #########################################OUTPUT WITH LOG LEVEL SET TO DEBUG IN BOTH CONFIG FILES ############################ ####################################### TEST NUMBER 0 ####################################### time taken in nanoseconds in first log4j test is 85486004 time taken in nanoseconds in second log4j test is 35743649 time taken in nanoseconds in first logback test is 22309540 time taken in nanoseconds in second logback test is 7795963 time taken in nanoseconds in third logback test is 19922365 ####################################### TEST NUMBER 1 ####################################### time taken in nanoseconds in first log4j test is 39167827 time taken in nanoseconds in second log4j test is 33095826 time taken in nanoseconds in first logback test is 3618616 time taken in nanoseconds in second logback test is 2657601 time taken in nanoseconds in third logback test is 6253309 ####################################### TEST NUMBER 2 ####################################### time taken in nanoseconds in first log4j test is 12328941 time taken in nanoseconds in second log4j test is 13580218 time taken in nanoseconds in first logback test is 2401422 time taken in nanoseconds in second logback test is 2868521 time taken in nanoseconds in third logback test is 4724902 ####################################### TEST NUMBER 3 ####################################### time taken in nanoseconds in first log4j test is 12460243 time taken in nanoseconds in second log4j test is 11747583 time taken in nanoseconds in first logback test is 2559543 time taken in nanoseconds in second logback test is 2694477 time taken in nanoseconds in third logback test is 4801727 ####################################### TEST NUMBER 4 ####################################### time taken in nanoseconds in first log4j test is 11915481 time taken in nanoseconds in second log4j test is 12330618 time taken in nanoseconds in first logback test is 2379073 time taken in nanoseconds in second logback test is 2888076 time taken in nanoseconds in third logback test is 2698667 ####################################### TEST NUMBER 5 ####################################### time taken in nanoseconds in first log4j test is 15098288 time taken in nanoseconds in second log4j test is 11025144 time taken in nanoseconds in first logback test is 8196013 time taken in nanoseconds in second logback test is 2065067 time taken in nanoseconds in third logback test is 2888076 ####################################### TEST NUMBER 6 ####################################### time taken in nanoseconds in first log4j test is 10594922 time taken in nanoseconds in second log4j test is 9976687 time taken in nanoseconds in first logback test is 2229892 time taken in nanoseconds in second logback test is 2172902 time taken in nanoseconds in third logback test is 2692800 ####################################### TEST NUMBER 7 ####################################### time taken in nanoseconds in first log4j test is 10521728 time taken in nanoseconds in second log4j test is 10123354 time taken in nanoseconds in first logback test is 2148597 time taken in nanoseconds in second logback test is 2135746 time taken in nanoseconds in third logback test is 2933893 ####################################### TEST NUMBER 8 ####################################### time taken in nanoseconds in first log4j test is 10182579 time taken in nanoseconds in second log4j test is 10013563 time taken in nanoseconds in first logback test is 2300851 time taken in nanoseconds in second logback test is 2087137 time taken in nanoseconds in third logback test is 2761803 ####################################### TEST NUMBER 9 ####################################### time taken in nanoseconds in first log4j test is 9720230 time taken in nanoseconds in second log4j test is 10646605 time taken in nanoseconds in first logback test is 2647264 time taken in nanoseconds in second logback test is 2164800 time taken in nanoseconds in third logback test is 2681905

3 5