November 2012 - logback-dev

[qos-ch/logback] 4807d5: LOGBACK-750 added missing stacktrace header lines ...
by Ceki Gulcu 13 Nov '12

13 Nov '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 4807d53ddd3425ba30f43b45641773a52c9e9713 https://github.com/qos-ch/logback/commit/4807d53ddd3425ba30f43b45641773a52c… Author: ingebrigt <ingebrigt(a)jpro.no> Date: 2012-09-19 (Wed, 19 Sep 2012) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/net/SyslogAppender.java Log Message: ----------- LOGBACK-750 added missing stacktrace header lines when logging stacktraces Commit: d3babf0d9dbc7235dc59824bd393d940bc778ce3 https://github.com/qos-ch/logback/commit/d3babf0d9dbc7235dc59824bd393d940bc… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-11-13 (Tue, 13 Nov 2012) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/net/SyslogAppender.java Log Message: ----------- Merge commit '4807d53ddd3425ba30f43b45641773a52c9e971' Commit: dae058dca833e7ac2c92b567785eb593ccc5648f https://github.com/qos-ch/logback/commit/dae058dca833e7ac2c92b567785eb593cc… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-11-13 (Tue, 13 Nov 2012) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/net/SyslogAppender.java M logback-classic/src/test/java/ch/qos/logback/classic/net/SyslogAppenderTest.java A logback-core/src/test/java/ch/qos/logback/core/recovery/ResilientOutputStreamTest.java Log Message: ----------- fix logback-750 Compare: https://github.com/qos-ch/logback/compare/1d87a2398b9a...dae058dca833

1 0

[JIRA] Created: (LBCLASSIC-279) Missing logging of Throwable in SyslogAppender
by Pasi Eronen (JIRA) 13 Nov '12

13 Nov '12

Missing logging of Throwable in SyslogAppender ---------------------------------------------- Key: LBCLASSIC-279 URL: http://jira.qos.ch/browse/LBCLASSIC-279 Project: logback-classic Issue Type: Bug Components: appender Affects Versions: 0.9.29 Reporter: Pasi Eronen Assignee: Logback dev list >From http://www.mail-archive.com/logback-dev@qos.ch/msg04990.html (Tobias Lund-Melcher, 05 October 2010): SyslogAppender does not seem to log the throwable type and its message at all. Tobias's message also included a patch. -- 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

2 1

[qos-ch/logback] 1d87a2: preparing relase 1.0.8
by Ceki Gulcu 13 Nov '12

13 Nov '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 1d87a2398b9a1ba85665442ae614043054150a32 https://github.com/qos-ch/logback/commit/1d87a2398b9a1ba85665442ae614043054… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-11-13 (Tue, 13 Nov 2012) Changed paths: M logback-access/pom.xml M logback-classic/pom.xml M logback-core/pom.xml M logback-examples/pom.xml M logback-site/pom.xml M logback-site/src/site/pages/news.html M pom.xml Log Message: ----------- preparing relase 1.0.8

1 0

[JIRA] (LOGBACK-765) ResilientFileOutputStream loses BufferedStream over recovery
by dpm (JIRA) 13 Nov '12

13 Nov '12

2 1

[qos-ch/logback] bc9369: update links
by Ceki Gulcu 13 Nov '12

13 Nov '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: bc93693cae1b4a3b5d049e182ba3bd105679456f https://github.com/qos-ch/logback/commit/bc93693cae1b4a3b5d049e182ba3bd1056… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-11-13 (Tue, 13 Nov 2012) Changed paths: M logback-site/src/site/pages/demo.html Log Message: ----------- update links Commit: 862b9ddda1d52b8a44efbb7352e54efbf1a75458 https://github.com/qos-ch/logback/commit/862b9ddda1d52b8a44efbb7352e54efbf1… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-11-13 (Tue, 13 Nov 2012) Changed paths: M logback-core/pom.xml M logback-core/src/main/java/ch/qos/logback/core/recovery/RecoveryCoordinator.java M logback-core/src/main/java/ch/qos/logback/core/recovery/ResilientFileOutputStream.java M logback-core/src/test/java/ch/qos/logback/core/FileAppenderResilienceTest.java M logback-core/src/test/java/ch/qos/logback/core/recovery/PackageTest.java M logback-core/src/test/java/ch/qos/logback/core/recovery/RecoveryCoordinatorTest.java M logback-core/src/test/java/ch/qos/logback/core/spi/AppenderAttachableImplLockTest.java M logback-site/src/site/pages/news.html Log Message: ----------- fix LOGBACK-765 Compare: https://github.com/qos-ch/logback/compare/3959ffb81a15...862b9ddda1d5

1 0

[JIRA] Created: (LBCLASSIC-325) Filtering out selected stack trace frames
by Tomasz Nurkiewicz (JIRA) 13 Nov '12

13 Nov '12

Filtering out selected stack trace frames ----------------------------------------- Key: LBCLASSIC-325 URL: http://jira.qos.ch/browse/LBCLASSIC-325 Project: logback-classic Issue Type: New Feature Components: appender, layout Reporter: Tomasz Nurkiewicz Assignee: Logback dev list Priority: Minor Many frameworks and libraries like Spring or EJB are introducing hundreds of synthetic method invocations (AOP, dynamic proxies, CGLIB-generated classes, etc.) They are irrelevant for most of the time and only cluttering the stack traces printed by Logback. It would be nice to have possibility to filter (possibly by providing a set of patterns in logback.xml) each stack trace line and skip selected ones. Similar feature is implemented in some IDEs, see: http://blogs.jetbrains.com/idea/2010/07/console-folding-customization. -- 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 6

[JIRA] (LOGBACK-762) Jansi fails on x64 Windows 7
by Bob Walker (JIRA) 12 Nov '12

12 Nov '12

2 2

[JIRA] Created: (LBCORE-171) Can't use logback on GAE SDK 1.3.7 when configured with logback.xml
by Maxim Veksler (JIRA) 10 Nov '12

10 Nov '12

Can't use logback on GAE SDK 1.3.7 when configured with logback.xml ------------------------------------------------------------------- Key: LBCORE-171 URL: http://jira.qos.ch/browse/LBCORE-171 Project: logback-core Issue Type: Bug Affects Versions: 0.9.24 Environment: GAE/J 1.3.7 Reporter: Maxim Veksler Assignee: Logback dev list Trying to initialize logback with custom configuration file (logback.xml) running on GAE platform throws the following exception Failed to instantiate [ch.qos.logback.classic.LoggerContext] Reported exception: java.lang.NoClassDefFoundError: java.net.InetAddress is a restricted class. Please see the Google App Engine developer's guide for more details. at com.google.appengine.tools.development.agent.runtime.Runtime.reject(Runtime.java:51) at ch.qos.logback.core.util.ContextUtil.getLocalHostName(ContextUtil.java:30) at ch.qos.logback.core.util.ContextUtil.addHostNameAsProperty(ContextUtil.java:39) at ch.qos.logback.classic.joran.action.ConfigurationAction.begin(ConfigurationAction.java:47) at ch.qos.logback.core.joran.spi.Interpreter.callBeginAction(Interpreter.java:273) at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:145) at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:127) at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:40) at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52) at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77) at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150) at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85) at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55) at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121) at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254) ...... This happens because ch.qos.logback.core.util.ContextUtil.java contains are reference to a java.net.InetAddress which is a restricted class on Google AppEngine Platform SDK 1.3.7: static String getLocalHostName() throws UnknownHostException { InetAddress localhost = InetAddress.getLocalHost(); return localhost.getHostName(); } I should note that BasicConfigurator is working and is able to configure the logback subsystem. A couple of resolutions I can think of: 1. Don't export this parameter by default, instead let the user choose if to define it or not in the logback.xml configuration file. 2. Create a "GAEConfigurator" which will use default for the limited GAE environment. 2. Provide a custom build for GAE platform, where this parameter will be taken from http://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api… or not be defined at all. 4. Provide some method to override / use a different implementation of ContextUtil, one which will be suitable for GAE. -- 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

2 2

[JIRA] (LOGBACK-760) Failed to instantiate LoggerContext
by Jaroslav Holubec (JIRA) 10 Nov '12

10 Nov '12

2 1

[JIRA] (LOGBACK-725) Logging System fails silently when config filename has an unsupported extension
by Ryan Scheidter (JIRA) 09 Nov '12

09 Nov '12

3 3