May 2008 - logback-user - mailman3.qos.ch

GPL+Classpath exception
by Anton Tagunov 30 May '08

30 May '08

Hello gentlemen, I've been very happy to discover SLF4J. Log4j has long needed a rework. SLF4J is a fresh wind :) It can blow Log4J out of the water. If it goes MIT me thinks. Ceki> Do we want Big Iron (insert your least favorite IT company here) Ceki> to legally pirate an open source project, say logback? As SLF4J gains popularity it will likely be perceived as same in kind to Log4J. However Big Co-s will rather "pirate" the conveniently licensed alternative. I don't see how Log4J can be replaced this way. IMO Logback needs MIT/ASL. cheers, Anton P.S. "cross-posting" to my blog :) http://atagunov.blogspot.com/2008/05/slf4j-beyond-log4j.html

2 4

TurboFilter scope
by Don Griffin 20 May '08

20 May '08

Firstly, as this is my first post, thanks for an overall great library! Having just read the section on TurboFilters, they are (almost) just what I need. I fear that the way they are implemented puts undue penalty and difficulty on their performance. I did scan the past several months in the archive and did not find any mention of TurboFilter, even still, this may be something someone else has already suggested. If so, I apologize for the noise. In any case, here is my suggestion: Why not put TurboFilters on Loggers instead of the global context? That is, the example from the (very helpful and well done) manual: <configuration> <turboFilter class="chapter6.SampleTurboFilter"> <Marker>sample</Marker> </turboFilter> <appender name="STDOUT" class="..."> ... snip ... </appender> <root> <appender-ref ref="STDOUT" /> </root> </configuration> Would change to: <configuration> <appender name="STDOUT" class="..."> ... snip ... </appender> <root> <turboFilter class="chapter6.SampleTurboFilter"> <Marker>sample</Marker> </turboFilter> <appender-ref ref="STDOUT" /> </root> </configuration> Almost the same, and it would achieve the same result as the original. In my case, however, I could apply a TurboFilter to only the loggers that need it: <configuration> <appender name="STDOUT" class="..."> ... snip ... </appender> <root> <appender-ref ref="STDOUT" /> </root> <logger name="foo"> <turboFilter class="chapter6.SampleTurboFilter"> <Marker>sample</Marker> </turboFilter> </logger> <logger name="foo.bar"> </logger> </configuration> In this case, the "foo.bar" logger would inherit the TurboFilter from the "foo" logger. In essence, each Logger object would have its own collection of TurboFilter objects that are the concatenation of any filters configured on itself, followed by its parent, grand-parent, etc. on up to the root of hierarchy. This approach should greatly reduce the total penalty for using such a powerful mechanism and at the same time give finer grained control over which filters apply to which loggers. Any thoughts? Best regards, Don

3 4

Migrated to JIRA
by Ceki Gulcu 20 May '08

20 May '08

The logback project now relies on to JIRA instead of Bugzilla as its bug tracking system. Previous bug reports as well existing users in Bugzilla have been migrated to JIRA. Thus, from now on, please use JIRA to create or edit bug reports. The url is: http://jira.qos.ch/ Let me know if you encounter any problems. -- Ceki Gülcü

1 0

logback and Jboss, impossible?
by Martyn Hiemstra 20 May '08

20 May '08

Hi All I have looked all over the Internet on how to get logback to work under Jboss. I have added the 3 jar files slf4j-api-1.5.0.jar, logback-core-0.9.9.jar and logback-classic-0.9.9.jar to my project. I can confirm that after deployment the files are in my projects WEB-INF\lib directory. I have created a logback.xml file and after deployment the file is in my projects WEB-INF\classes directory. I start up jboss and my application works perfectly except logback. No matter what I do, It just wont initialize. I have no logging to the console or log files what so ever. My logback.xml file: <?xml version="1.0" encoding="UTF-8"?> <configuration> <appender class="ch.qos.logback.core.rolling.RollingFileAppender" name="RootFileAppender"> <append>true</append> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>debug</level> </filter> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>mylogfile.nl.%d{yyyy-MM-dd}.gz</fileNamePattern> </rollingPolicy> <layout class="ch.qos.logback.classic.html.HTMLLayout"> <pattern>%d{yyyy-MM-dd HH:mm:ss}%p%t%ex%F%L%C{1}%M %m</pattern> </layout> </appender> <appender class="ch.qos.logback.core.ConsoleAppender" name="RootConsoleAppender"> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>debug</level> </filter> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%d{yyyy-MM-dd HH:mm:ss},%p,%c,%t,%ex,%F,%L,%C{1},%M %m%n</pattern> </layout> </appender> <root> <level value="debug"/> <appender-ref ref="RootFileAppender"/> <appender-ref ref="RootConsoleAppender"/> </root> </configuration> Thanks in advance, Martyn

2 3

Configuring logback with variable substitution
by øyvind rotnes 14 May '08

14 May '08

Hi people! I have an issue. I want to use variable substitution to configure logback.xml, which works fine. But I also want to set substitutionProperty file value with the java -D argument when I start up my server. Some thing lige this: java -Dlogback.config="/path/to/my/property/file" <configuration debug="true"> <substitutionProperty file=${logback.properties} />

1 1

configuring logback to log to two different
by øyvind rotnes 12 May '08

12 May '08

Hi. I am new to logback and have some problem with setting up the configuration. I want to add some new functionality to the existing logging configuration that was already in use in the application. I want my application to write log events from the classes that are in the package: "com.my.package" to a FILE >From the documentation I undestod that this can be done with <logger additivity="false" name="com.my.package"> <level value="debug" /> <appender-ref ref="FILE" /> </logger> which points to a file appender. My logback.xml is listet below. This configuration prints everything to the console, but nothing to the FILE. Can someone please point out for me where i am doing wrong? Thanks! <configuration debug="true"> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>c:\temp\testAction.log</File> <append>true</append> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <FileNamePattern>testAction.%i.log.zip</FileNamePattern> <MinIndex>1</MinIndex> <MaxIndex>3</MaxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <MaxFileSize>5MB</MaxFileSize> </triggeringPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%date{yyyy-MM-dd HH:mm:ss.SSS} %X{action} %msg%n</Pattern> </layout> </appender> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%msg%n</Pattern> </layout> </appender> <logger additivity="false" name="com.my.package"> <level value="debug" /> <appender-ref ref="FILE" /> </logger> <root> <level value="debug" /> <appender-ref ref="STDOUT" /> </root> </configuration>

3 3

Manfred Kuhlmann is out of office.
by Manfred.Kuhlmann＠steria-mummert.de 01 May '08

01 May '08

Ich werde ab dem 30.04.2008 nicht im Büro sein. Ich kehre zurück am 05.05.2008. I will be out of the office starting 30.04.2008. I will be back on 05.05.2008. Ihre Nachricht werde ich nach meiner Rückkehr beantworten. I will answer your message after my return. Mit freundlichen Grüßen Best regards Manfred Kuhlmann

1 0

MDC performance concerns
by Matthew Finn 01 May '08

01 May '08

Hello, I am interested in converting my application to logback, but I have some performance concerns about its MDC implementation. My application uses MDC extensively for async IO, so it may call MDC.put and MDC.remove extremely frequently, because each thread may be handling 1000s of interleaved connections using state machines. I see in the source for LogbackMDCAdapter that for every call to MDC.put and MDC.remove, the HashMap is cloned. Could this clone potentially be handled during the creation of LoggingEvents instead of the call to MDC? The creation of logging events is expected to entail memory allocation, so it seems that it would be a better fit there, even if some applications might have a very low number of calls to MDC versus logging calls. It seems that the same energy expended in minimizing log statement impact when logging is turned off should also apply to MDC calls. Thanks Matt

2 2