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

[JIRA] Created: (LBACCESS-29) Getting Java java.lang.ClassNotFound except with v1.0.0 & Jetty 7
by Ian Stewartson (JIRA) 22 Jun '12

22 Jun '12

Getting Java java.lang.ClassNotFound except with v1.0.0 & Jetty 7 ----------------------------------------------------------------- Key: LBACCESS-29 URL: http://jira.qos.ch/browse/LBACCESS-29 Project: logback-access Issue Type: Bug Affects Versions: 1.0.0 Environment: Linux RedHat 5.7 (2.6.18-274.3.1.el5) Jetty: jetty-7.5.1.v20110908 - 08 September 2011 java version "1.6.0_27" logback-access-1.0.0.jar logback-core-1.0.0.jar Reporter: Ian Stewartson Assignee: Logback dev list Have following installation instructions on Web page, however, get an exception when starting Jetty: 2011-11-28 09:35:50.809:WARN:oejx.XmlConfiguration:Config error at <Set name="requestLog">| <New id="requestLogImpl" class="ch.qos.logback.access.jetty.RequestLogImpl"/>| </Set> java.lang.ClassNotFoundException: ch.qos.logback.access.jetty.RequestLogImpl 2011-11-28 09:35:50.809:WARN:oejx.XmlConfiguration:Config error at <Ref id="RequestLogHandler"><Set name="requestLog">| <New id="requestLogImpl" class="ch.qos.logback.access.jetty.RequestLogImpl"/>| </Set></Ref> java.lang.ClassNotFoundException: ch.qos.logback.access.jetty.RequestLogImpl java.lang.reflect.InvocationTargetException jetty.xml contents:    <Set name="handler"> <New id="Handlers" class="org.eclipse.jetty.server.handler.HandlerCollection"> <Set name="handlers"> <Array type="org.eclipse.jetty.server.Handler"> <Item> <New id="Contexts" class="org.eclipse.jetty.server.handler.ContextHandlerCollection"/> </Item> <Item> <New id="DefaultHandler" class="org.eclipse.jetty.server.handler.DefaultHandler"/> </Item>  <Item> <New id="RequestLogHandler" class="org.eclipse.jetty.server.handler.RequestLogHandler"/> </Item> </Array> </Set> </New> </Set>    <Ref id="RequestLogHandler"> <Set name="requestLog"> <New id="requestLogImpl" class="ch.qos.logback.access.jetty.RequestLogImpl"> </New> </Set> </Ref> -- 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 4

[JIRA] Created: (LBCLASSIC-307) Logback is unable to recognize variable substitution for scanPeriod property
by Oh Chin Boon (JIRA) 12 Jun '12

12 Jun '12

Logback is unable to recognize variable substitution for scanPeriod property ---------------------------------------------------------------------------- Key: LBCLASSIC-307 URL: http://jira.qos.ch/browse/LBCLASSIC-307 Project: logback-classic Issue Type: Bug Components: Other Affects Versions: 0.9.30 Environment: Windows 7 Reporter: Oh Chin Boon Assignee: Logback dev list It seems like Logback is unable to recognize variable substitution for certain properties. For example the scanPeriod property: Logback configuration: <configuration scan="${scan:-true}" scanPeriod="${scan-interval:-10 minutes}"> Specified to take default value of 10 minutes of logback property is not defined. Logback properties: scan=true scan-interval=30 seconds This property should override the default configuration of 10 minutes. Logback error: java.lang.IllegalArgumentException: String value [${scan-interval:-10 minutes}] is not in the expected format. According to the Duration API, the duration format is correct. -- 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] Created: (LBCLASSIC-74) NullPointerException in Logger after container restart
by Manel Clos (JIRA) 11 Jun '12

11 Jun '12

NullPointerException in Logger after container restart ------------------------------------------------------ Key: LBCLASSIC-74 URL: http://jira.qos.ch/browse/LBCLASSIC-74 Project: logback-classic Issue Type: Bug Affects Versions: 0.9.9 Environment: Eclipse 3.4, Java 5, Tomcat 5.5.26, plain JSP (no servlet) Reporter: Manel Clos Assignee: Logback dev list Hi, loggerContext in the Logger class is null after container restart. This will produce a NPE when trying to further use logback. java.lang.NullPointerException at ch.qos.logback.classic.Logger.callTurboFilters(Logger.java:775) at ch.qos.logback.classic.Logger.isDebugEnabled(Logger.java:630) at ch.qos.logback.classic.Logger.isDebugEnabled(Logger.java:613) at test.LogbackTest.testLogger(LogbackTest.java:15) -- 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 8

[qos-ch/logback] 91ffa4: minor optimization
by Ceki Gulcu 31 May '12

31 May '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 91ffa4f9f9a2399343554a1b6791baa601f70706 https://github.com/qos-ch/logback/commit/91ffa4f9f9a2399343554a1b6791baa601… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-05-31 (Thu, 31 May 2012) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/net/SyslogAppender.java Log Message: ----------- minor optimization

1 0

[JIRA] (LBCLASSIC-333) add stacktraceSuffixPattern
by Ingebrigt Berg (JIRA) 31 May '12

31 May '12

2 3

[qos-ch/logback] 246567: start working on 1.0.5-SNAPSHOT
by Ceki Gulcu 31 May '12

31 May '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 2465675e48b70f07c268ede3158cca7b1d8ce2d8 https://github.com/qos-ch/logback/commit/2465675e48b70f07c268ede3158cca7b1d… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-05-31 (Thu, 31 May 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 pom.xml Log Message: ----------- start working on 1.0.5-SNAPSHOT

1 0

[qos-ch/logback]
by ceki 31 May '12

31 May '12

Branch: refs/tags/v_1.0.4 Home: https://github.com/qos-ch/logback

1 0

[qos-ch/logback] a773d9: minor correction
by Ceki Gulcu 31 May '12

31 May '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: a773d9620f052a024285589c93cec345cddaab6b https://github.com/qos-ch/logback/commit/a773d9620f052a024285589c93cec345cd… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-05-31 (Thu, 31 May 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: ----------- minor correction

1 0

Release of logback version 1.0.4
by ceki 31 May '12

31 May '12

Hello all, I am thrilled to announce the release of logback version 1.0.4. 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

[JIRA] Created: (LBCLASSIC-327) SyslogAppender doesn't respect %nopex, outputs stack trace
by Don Faulkner (JIRA) 31 May '12

31 May '12

SyslogAppender doesn't respect %nopex, outputs stack trace ---------------------------------------------------------- Key: LBCLASSIC-327 URL: http://jira.qos.ch/browse/LBCLASSIC-327 Project: logback-classic Issue Type: Bug Components: appender, layout Affects Versions: 1.0.0 Environment: Ubuntu (11.10) & Red Hat (RHEL 5.8) Linux, Java 1.6, Shibboleth Identity Provider 2.3.6 Reporter: Don Faulkner Assignee: Logback dev list (See http://mailman.qos.ch/pipermail/logback-user/2012-April/003096.html) When using SyslogAppender, stack trace output appears in the output of the Appender, contrary to the configured (or programmed) layout. When my SyslogAppender is used, stack traces appear in my syslog output, even though I don't want them. I've included a "%nopex" at the end of the SuffixPattern value, but this has not stopped the stack traces from appearing. I've tested a matching RollingFileAppender, where "%nopex" has the expected behavior. I'd expect that SyslogAppender would omit stack traces by default, or at least give me a way to omit them. I've looked at the source for SyslogAppender.java, and I see (about line 43) that the prefixPattern already includes "%nopex" so I'm at a loss as to why I'm seeing stack traces to begin with. I've configured a SyslogAppender as follows. The "%nopex" at the end doesn't matter. I can leave it out with identical results. The blank space at the beginning of SuffixPattern doesn't matter either. I can leave it out with identical results. <appender name="IDP_SYSLOG" class="ch.qos.logback.classic.net.SyslogAppender"> <SyslogHost>localhost</SyslogHost> <Port>514</Port> <Facility>AUTH</Facility> <SuffixPattern> [%logger:%level] %msg %mdc{idpSessionId} from %mdc{clientIP}%nopex</SuffixPattern> </appender> -- 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

5 4