July 2012 - logback-dev - mailman3.qos.ch

[JIRA] Created: (LBCLASSIC-212) Logback classic doesn't work with Tomcat
by Grzegorz Borkowski (JIRA) 21 Aug '12

21 Aug '12

Logback classic doesn't work with Tomcat ---------------------------------------- Key: LBCLASSIC-212 URL: http://jira.qos.ch/browse/LBCLASSIC-212 Project: logback-classic Issue Type: Bug Affects Versions: 0.9.21 Reporter: Grzegorz Borkowski Assignee: Logback dev list Priority: Critical We have a web application running on Tomcat 6.0.26, which uses SLF4J for logging. Until now, we used SLF4J-Simple, and it worked very well. Now we try to switch to Logback, but we are not able to make it work. It works for logging one-line messages. But whenever any exception is thrown on server, which should print a stack trace, server hangs (It doesn't matter whether we actually print the stack trace in log or not). From what I was able to observe, it looks like it falls into endless loop, throwing "ClassNotFoundException: ch.qos.logback.classic.spi.ThrowableProxyUtil", which is caught and tried to be logged, which throws this exception again, and so on. I don't know why it throws this ClassNotFoundException - perhaps classloader issue? But even copying the logback jars to Tomcat's lib directory, I'm not able to run the application: than it has problems with starting up. Sometimes it freezes during loading web app, and often it helps to attach and detach debugger to Tomcat - it's a kind of magic... Anyway, it's horrendously painful, and I'm not able to make it work. Why such common setup (webapp on Tomcat) is not described in Logback documentation??? This is our configuration file : <configuration scan="true"> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">  <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n%ex</pattern> </encoder> </appender> <root level="info"> <appender-ref ref="STDOUT" /> </root> </configuration> (changing scan to "false" doesn't help. Also changing pattern to the one not containing "%ex" doesn't help) This is part of pom file related to logging: <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>1.6.0</version> </dependency> <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>0.9.21</version> <scope>runtime</scope> </dependency>  <dependency> <groupId>commons-logging</groupId> <artifactId>commons-logging</artifactId> <version>1.1.1</version> <scope>provided</scope> </dependency>  <dependency> <groupId>org.slf4j</groupId> <artifactId>jcl-over-slf4j</artifactId> <version>1.6.0</version> </dependency> If we change dependency from logback to SLF4J simple (1.6.0) than everything works smoothly, stacktraces are printed to console, no freezing, everything is perfect. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

6 21

[JIRA] Created: (LBCORE-252) Logback groovy configuration add support for Perf4j
by Muyen Lee (JIRA) 09 Aug '12

09 Aug '12

Logback groovy configuration add support for Perf4j ---------------------------------------------------- Key: LBCORE-252 URL: http://jira.qos.ch/browse/LBCORE-252 Project: logback-core Issue Type: Improvement Components: Appender Reporter: Muyen Lee Assignee: Logback dev list Priority: Minor I want to add an AsyncCoalescingStatisticsAppender. The XML confugration looks like this. <appender name="CoalescingStatistics" class="org.perf4j.logback.AsyncCoalescingStatisticsAppender"> <param name="TimeSlice" value="60000"/> <appender-ref ref="graphExecutionTimes"/> <appender-ref ref="graphExecutionTPS"/>  <appender-ref ref="perf4jJmxAppender"/> </appender> logback.groovy's appender function doesn't support <appender-ref ref="perf4jJmxAppender"/> The workaround is to write groovy directly JmxAttributeStatisticsAppender jmxAppender = new JmxAttributeStatisticsAppender() jmxAppender.name = "Per4j" jmxAppender.context = context jmxAppender.tagNamesToExpose="tag1, tag2" appenderList.add(jmxAppender) AsyncCoalescingStatisticsAppender coalAppender = new AsyncCoalescingStatisticsAppender() // in millisecond coalAppender.timeSlice=10000 coalAppender.name = "CoalescingStatistics" coalAppender.context = context coalAppender.addAppender(jmxAppender) appenderList.add(coalAppender) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

3 2

[JIRA] (LOGBACK-719) Provide a mechanism to specify an appender factory class
by Rich Mayfield (JIRA) 01 Aug '12

01 Aug '12

2 13

Organizing loggers per function/mechanism rather than per class
by Cristian SPIESCU 30 Jul '12

30 Jul '12

Hello all, I would like to change the way messages are logged in my current application. Now, all the loggers are defined in the "classic" way: a logger per class, that is named according to the owning class. For the features/functions/mechanisms that span their execution among multiple classes, it's more convenient to organize the log per those specific roles that they play in the application. Let me give you an example. * Class: ServerEndpoint having 2 methods: deserialize(), executeLogic(). * Class: ServerLogicUnit having 2 similar methods: deserialize(), executeLogic(). I'd like both methods: ServerEndpoin.deserialize() and ServerLogicUnit.deserialize() (+ subclasses eventually) to use a logger, let's say: "server.processing.deserialization". In a similar way, ServerEndpoint.executeLogic() and ServerLogicUnit.executeLogic() would use "server.processing.execution". I see 2 solutions for this. 1) Have loggers that are registered like this: static public Logger loggerSerialization = LoggerFactory.getLogger("server.processing.deserialization"); static public Logger loggerExecution = LoggerFactory.getLogger("server.processing.execution"); This loggers are stored somewhere kind of globally, and different pieces of code, from various classes use them for logging. 2) I guess a solution can be found, even if the loggers are stored per class, using markers or MDC + some custom filtering logic. My question: what are the best practices in this area? Are there possible issues if I'll go for "Solution 1"? I'm realizing that I instantiate one logger per class somehow by reflex, not as result of a need. When I need to activate the log in a production application, to see what happens with a certain mechanism of the application, I end up in enabling debug or trace for the whole app. This shows me what I need, but it pollutes my log terribly. Thank you in advance for you feedback. Best regards, Cristian.

1 0

[qos-ch/logback-beagle] 4ac654: repopulate grid after filtering changes
by Ceki Gulcu 29 Jul '12

29 Jul '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-beagle Commit: 4ac654cb44f88440ea56349b68590093d9d7f428 https://github.com/qos-ch/logback-beagle/commit/4ac654cb44f88440ea56349b685… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-07-29 (Sun, 29 Jul 2012) Changed paths: R ch.qos.logback.beagle/src/ch/qos/logback/beagle/HideMain.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/LoggerTree.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/TreeMain.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/TreeMenuBuilder.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/TreeMenuSelectionListener.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/view/TableMediator.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/visual/ClassicTISBuffer.java Log Message: ----------- repopulate grid after filtering changes

1 0

[JIRA] (LOGBACK-726) Aggregating multiple logback.xml configurations
by Ryan (JIRA) 29 Jul '12

29 Jul '12

1 2

[qos-ch/logback-beagle] f3f30b: logger tree placed in the view
by Ceki Gulcu 28 Jul '12

28 Jul '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-beagle Commit: f3f30b390d139fb581b6807ee6a3f06c0ec67373 https://github.com/qos-ch/logback-beagle/commit/f3f30b390d139fb581b6807ee6a… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-07-28 (Sat, 28 Jul 2012) Changed paths: M ch.qos.logback.beagle.tests/src/ch/qos/logback/beagle/vista/MyMain.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/Constants.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/menu/DynamicMenuEnabler.java A ch.qos.logback.beagle/src/ch/qos/logback/beagle/menu/GridMenuBuilder.java R ch.qos.logback.beagle/src/ch/qos/logback/beagle/menu/MenuBuilder.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/menu/OnMenuSelectionAction.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/net/EventConsumerThread.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/net/LoggingEventSocketServer.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/LoggerTree.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/TreeMain.java A ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/TreeMenuBuilder.java A ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/TreeMenuSelectionListener.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/view/BeagleView.java A ch.qos.logback.beagle/src/ch/qos/logback/beagle/view/SashListener.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/view/TableMediator.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/visual/ClassicTISBuffer.java M logback-beagle.target Log Message: ----------- logger tree placed in the view

1 0

[qos-ch/logback-beagle] 25889e: ongoing work on logger tree
by Ceki Gulcu 27 Jul '12

27 Jul '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-beagle Commit: 25889ee19e9bff614649dd595765e8aef8b23c56 https://github.com/qos-ch/logback-beagle/commit/25889ee19e9bff614649dd59576… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-07-27 (Fri, 27 Jul 2012) Changed paths: A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/D-16x16.png A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/D-24x24.png A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/E-16x16.png A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/E-24x24.png A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/I-16x16.png A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/I-24x24.png A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/T-16x16.png A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/T-24x24.png A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/W-16x16.png A ch.qos.logback.beagle/icons/ch/qos/logback/beagle/icons/W-24x24.png M ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/LoggerTree.java A ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/TreeMain.java M ch.qos.logback.beagle/src/ch/qos/logback/beagle/util/ResourceUtil.java Log Message: ----------- ongoing work on logger tree

1 0

Logging plain text to an tcp socket
by Benjamin Leov 27 Jul '12

27 Jul '12

Hi Developers! Im looking for a way of connecting logback to nxlog. As nxlog does not have direct support for logback, the easiest way I can think of doing it would be via a plain text connection. However, without writing custom code (which isn't an option as I want to use this in many existing applications), I can see no way of doing that. Have I missed something? What would be really nice would be to allow the SocketAppender to take an encoder. Any help would be much appreciated! Regards, Ben

1 0

[qos-ch/logback-beagle] 394a50: Update the project version to 1.1.0.qualifier.
by Ceki Gulcu 27 Jul '12

27 Jul '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-beagle Commit: 394a5090c7009ca500f5a4df6797ec4455c3e76d https://github.com/qos-ch/logback-beagle/commit/394a5090c7009ca500f5a4df679… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-07-27 (Fri, 27 Jul 2012) Changed paths: M ch.qos.logback.beagle.feature/feature.xml M ch.qos.logback.beagle.feature/pom.xml M ch.qos.logback.beagle.repository/category.xml M ch.qos.logback.beagle.repository/pom.xml M ch.qos.logback.beagle.tests/META-INF/MANIFEST.MF M ch.qos.logback.beagle.tests/pom.xml M ch.qos.logback.beagle/META-INF/MANIFEST.MF M ch.qos.logback.beagle/pom.xml M ch.qos.logback.beagle/src/ch/qos/logback/beagle/tree/LoggerTree.java M pom.xml Log Message: ----------- Update the project version to 1.1.0.qualifier. Using logback-classic version 1.0.7-SNAPSHOT obtained from http://logback.qos.ch/p2/proper-nightly Starting work on logger tree

1 0