- logback-user - mailman3.qos.ch

Release of logback version 1.0.3
by ceki 07 May '12

07 May '12

Hello all, I am happy to announce the release of logback version 1.0.3. It should hit the Maven central repository within the next 24 hours. Please refer to the news page for precise details of this release. 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 http://twitter.com/#!/ceki

2 3

Inverse log4j-over-slf4j?
by Mike Boyers 07 May '12

07 May '12

We have a project that uses slf4j/logback for its logging. We have dependencies we're pulling in that are using log4j, so for that, we're using the log4j-over-slf4j bridge. We have a single logback.xml configuration that controls it all, and everything is fine. But we publish artifacts, and other projects have our artifacts as their dependencies, and they are using log4j strictly. Let's assume they know nothing about logback and have no desire to switch. What technique to people typically follow in this case? Is there an inverse log4j-over-slf4j bridge? Thanks, Mike

3 3

Re: [logback-user] Setting log LEVEL on a per <appender-ref/> basis
by Shane Kelly 06 May '12

06 May '12

Hi Ceki, Thanks for your prompt response. I wasn't aware of routing appenders - so this is something that I shall certainly look into. My main motivation for wanting to do this was primarily so that I could control the verboseness of logging for the same logger depending on the destination appender without having to create several (almost duplicate) appender configurations (whilst setting slightly different threshold levels for each) - as far as possible I only wanted to create a single appender configuration entry for each distinct destination - i.e. Console, RollingFile etc. So, for example, I might have a logger in a Java class which generates log messages of varying levels, but I only want INFO and above to go to a Console appender, whilst I want DEBUG and above to be written to a RollingFileAppender - for the same class - simply because I don't want to clog up STDOUT with too much information (unless I need to) but have a separate file to fall back to which does contain a complete set of log messages for reference/debug at a later date. Is there any documentation describing how to create routing appenders (I had a quick look and couldn't see anything) or is there an example of such an appender lurking somewhere within the source that you could point me towards? Regards, Shane > Hello Shane, > > There are probably multiple approaches to this problem. It should be not > too difficult to write a RoutingAppender which can perform the type of > routing operation you describe. Here is how the config file would look like: > > <appender name="A"></appender> > <appender name="B"></appender> > > <appender name="ROUTING-ONE" class="...RoutingAppender"> > <reference name="A" level="INFO"/> > <reference name="B" level="DEBUG"/> > </appender> > > <appender name="ROUTING-TWO" class="...RoutingAppender"> > <reference name="A" level="WARN"/> > <reference name="B" level="TRACE"/> > </appender> > > <logger name="com.myorg.myapp.**subpackage.one"> > <appender-ref ref="ROUTING-ONE"/> > </logger> > > <logger name="com.myorg.myapp.**subpackage.two"> > <appender-ref ref="ROUTING-TWO"/> > </logger> > > > By the way, could you provide more detail for your use case? > > Cheers, > -- > Ceki > http://twitter.com/#!/ceki > > > On 05.05.2012 22:48, Shane Kelly wrote: > >> Folks, >> >> I've been tinkering with both log4j and more recently logback and I was >> wondering whether or not it is possible to configure it in such a way >> that it would be possible for a single logger to write to multiple >> appenders using different LEVEL restrictions on a per-appender-ref >> basis. I appreciate that it is possible to specify a LEVEL attribute for >> each individual logger - but then any message which meets the logger >> LEVEL criteria will be sent to all referenced appenders. I'm also aware >> that you can define level thresholds and filters on a per-appender basis >> - but what I was hoping for was rather than define lots of very similar >> appender configurations (each with slightly different thresholds) that I >> could define a smaller number of core appenders and have messages of >> certain levels filtered out even before the appender is called. >> >> To help illustrate the concept I'm aiming for, I've included a >> pseudo-configuration file below. You'll notice that I've omitted the >> LEVEL attribute from the <logger/> nodes and added LEVEL attributes to >> each of the <appender-ref> nodes - this doesn't work obviously, but I >> was wondering if there was some other way of emulating the behaviour >> that I'm after without cluttering up the logback configuration too >> much...? You can see from the configuration that for >> com.myorg.myapp.subpackage.one I would like to apply different log level >> restrictions depending on the destination appender. You'll also notice >> that for com.myorg.myapp.subpackage.two I want to reuse the same >> appenders, but also use different level restrictions.... hope that makes >> it clear enough... >> >> --------- >> >> <appender name="A"> >> ... >> ... >> </appender> >> >> <appender name="B"> >> ... >> ... >> </appender> >> >> <logger name="com.myorg.myapp.**subpackage.one"> >> <appender-ref ref="A" LEVEL="INFO"/> >> <appender-ref ref="B" LEVEL="DEBUG"/> >> </logger> >> >> <logger name="com.myorg.myapp.**subpackage.two"> >> <appender-ref ref="A" LEVEL="WARN"/> >> <appender-ref ref="B" LEVEL="TRACE"/> >> </logger> >> >> ---------- >> >> Regards, >> >> Shane >> >> > ______________________________**_________________ > Logback-user mailing list > Logback-user(a)qos.ch > http://mailman.qos.ch/mailman/**listinfo/logback-user<http://mailman.qos.ch/mailman/listinfo/logback-user> > >

2 2

Setting log LEVEL on a per <appender-ref/> basis
by Shane Kelly 05 May '12

05 May '12

Folks, I've been tinkering with both log4j and more recently logback and I was wondering whether or not it is possible to configure it in such a way that it would be possible for a single logger to write to multiple appenders using different LEVEL restrictions on a per-appender-ref basis. I appreciate that it is possible to specify a LEVEL attribute for each individual logger - but then any message which meets the logger LEVEL criteria will be sent to all referenced appenders. I'm also aware that you can define level thresholds and filters on a per-appender basis - but what I was hoping for was rather than define lots of very similar appender configurations (each with slightly different thresholds) that I could define a smaller number of core appenders and have messages of certain levels filtered out even before the appender is called. To help illustrate the concept I'm aiming for, I've included a pseudo-configuration file below. You'll notice that I've omitted the LEVEL attribute from the <logger/> nodes and added LEVEL attributes to each of the <appender-ref> nodes - this doesn't work obviously, but I was wondering if there was some other way of emulating the behaviour that I'm after without cluttering up the logback configuration too much...? You can see from the configuration that for com.myorg.myapp.subpackage.one I would like to apply different log level restrictions depending on the destination appender. You'll also notice that for com.myorg.myapp.subpackage.two I want to reuse the same appenders, but also use different level restrictions.... hope that makes it clear enough... --------- <appender name="A"> ... ... </appender> <appender name="B"> ... ... </appender> <logger name="com.myorg.myapp.subpackage.one"> <appender-ref ref="A" LEVEL="INFO"/> <appender-ref ref="B" LEVEL="DEBUG"/> </logger> <logger name="com.myorg.myapp.subpackage.two"> <appender-ref ref="A" LEVEL="WARN"/> <appender-ref ref="B" LEVEL="TRACE"/> </logger> ---------- Regards, Shane

2 1

SMTPAppender mail not sent (logback 1.0.0, JDK 1.5)
by Louis-Félix 03 May '12

03 May '12

Hi, I upgraded to logback 1.0.0 in a web application (tomcat 5, JDK 1.5), and the ERROR email are not sent anymore from the SMTPAppender. When I rollback my logback-core and logback-classic JARs to version 0.9.30, it's working again. I have a simple config: <appender name="courriel" class="ch.qos.logback.classic.net.SMTPAppender"> <smtpHost>smtp.xxx.xx.xx</smtpHost> <to>xxx(a)xxx.xx.xx</to> <from>no-reply.ti(a)xxx.xx.xx</from> <subject>Test</subject> <cyclicBufferTracker class="ch.qos.logback.core.spi.CyclicBufferTrackerImpl"> <bufferSize>25</bufferSize> </cyclicBufferTracker> <layout class="ch.qos.logback.classic.html.HTMLLayout"> <pattern>%date%level%thread%logger%line%message</pattern> </layout> </appender> I am using logback 1.0.0 with no problem in an other project (with JDK 1.6). Is there any known compatibility problem between logback 1.0.0 and JDK 1.5? Thanks, Louis-Félix

6 10

SMTPAppender mail not sent (logback 1.0.0, JDK 1.5)
by Dave 03 May '12

03 May '12

I've found the source of the SMTPAppender issues. It with the ThreadPoolExecutor defined in the ContextBase class // 0 idle threads, 2 maximum threads, no idle waiting ExecutorService executorService = new ThreadPoolExecutor(0, 2, 0L, TimeUnit.MILLISECONDS, new LinkedBlockingQueue<Runnable>()); If you increase the first parameter (which is the initial pool size) from 0 to 2, then it works as expected in both JRE 1.5 and 1.6. -dave

2 1

Multiple logback config files warning
by Adam Gordon 02 May '12

02 May '12

We have different logback config files, one for testing and one for production. I just noticed a warning during a maven install that logback found multiple config files, one under target/test-classes and the other under target/classes. Is this a concern? Does logback use the first config file it finds and will it always find the test file first? If not, and I realize this is may be a maven question, how do I configure maven to only use the logback file under test-classes when running the unit tests as part of the maven install command? Thanks, --adam http://gordonizer.com

2 2

set outputPatternAsPresentationHeader programatically?
by Andrzej Zadorozny 02 May '12

02 May '12

Hello. Just letting you know that logback is awesome, and I like it a lot. I have a quick question regarding the new release. Is there a way to set 'outputPatternAsPresentationHeader' to 'false' programatically? I get the default pattern output to stdout even before I get my hands on the logger context: ILoggerFactory factory = LoggerFactory.getILoggerFactory(); So by the time I get to even begin to configure my own layout, the pattern of the default layout is already on the screen (and it's not even the pattern that I'm trying to configure). Also the link on the web page to "one-question survey" appears to be broken. I would like to suggest to leave that option as 'false' by default, and give the ability for people to turn it on when they need to. Otherwise, logback is awesome, and I am looking forward to new features and enhancements. Thank you very much. :) CheerZ! :)

2 2

"#logback.classic pattern:" spam in 1.0.2
by tsuna 02 May '12

02 May '12

Hi list, I just upgraded from logback-{core,classic} 1.0.0 to 1.0.2 and now whenever I start my application I see a message like this one: #logback.classic pattern: %msg%n in my logs. Like, really, it's literally logging the format string itself. Has a debug statement slipped in the 1.0.2 release? Here's the configuration of the app, in case you need it: <?xml version="1.0" encoding="UTF-8"?> <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern> %d{ISO8601} %-5level [%thread] %logger{0}: %msg%n </pattern> </encoder> </appender> <appender name="ACCESS" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>logs/access.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>logs/access.%d{yyyy-MM-dd}.%i.log.gz</fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>1GB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> <maxHistory>45</maxHistory> </rollingPolicy> <encoder> <pattern>%msg%n</pattern> </encoder> </appender> <logger name="access.log" additivity="false"> <appender-ref ref="ACCESS"/> </logger> <root level="info"> <appender-ref ref="STDOUT"/> </root> </configuration> When I start my app, before my main() starts, I see this on the STDOUT console logger: #logback.classic pattern: %d{ISO8601} %-5level [%thread] %logger{0}: %msg%n And this gets added to my logs/access.log: #logback.classic pattern: %msg%n Thanks in advance. -- Benoit "tsuna" Sigoure Software Engineer @ www.StumbleUpon.com

4 6

Release of logback version 1.0.2
by ceki 26 Apr '12

26 Apr '12

Hello all, I am happy to announce the release of logback version 1.0.2. It should hit the Maven central repository within the next 24 hours. Please refer to the news page for precise details of this release. 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 http://twitter.com/#!/ceki

1 0