- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-764) Allow context configuration through Java class
by Mark A. Ziesemer (JIRA) 25 Oct '12

25 Oct '12

1 0

[JIRA] (LOGBACK-763) LayoutWrappingEncoder.isStarted() Always returns false
by dpm (JIRA) 25 Oct '12

25 Oct '12

1 0

How to contribute to logback?
by Becker, Thomas 25 Oct '12

25 Oct '12

I've cloned logback on github and implemented an RFE that I filed. I went ahead and submitted a pull request, https://github.com/qos-ch/logback/pull/63, though I noticed that there are a lot of outstanding pull requests that don't seem to be getting addressed. Is there something that developers looking to contribute back need to do, or is it the dev's intention not to accept contributions from the community? With regard to this change specifically, we could obviously just use my forked copy, but we would prefer to utilize an official released version, and I do feel that other people could benefit from the changes. Regards, Tommy Becker

2 5

[JIRA] Created: (LBCLASSIC-230) %cn conversion word fails in SMTPAppender subject
by Michael Osipov (JIRA) 24 Oct '12

24 Oct '12

%cn conversion word fails in SMTPAppender subject ------------------------------------------------- Key: LBCLASSIC-230 URL: http://jira.qos.ch/browse/LBCLASSIC-230 Project: logback-classic Issue Type: Bug Components: layout Affects Versions: 0.9.26 Reporter: Michael Osipov Assignee: Logback dev list According to the docs, the subject pattern equals to the pattern layout. Putting a %cn into it fails with an exception {noformat} <Subject>${HOSTNAME} %cn %level %X{ad.displayName} %logger{20} - %.20msg - %ex{-1}</Subject> {noformat} {noformat} 15:13:56,973 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.net.SMTPAppender] 15:13:57,045 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [EMAIL] 15:13:57,525 |-ERROR in ch.qos.logback.core.pattern.parser.Compiler@1a54421 - Failed to instantiate converter class [ch.qos.logback.classic.joran.action.ContextNameAction] ch.qos.logback.core.util.IncompatibleClassException at ch.qos.logback.core.util.IncompatibleClassException at at ch.qos.logback.core.util.OptionHelper.instantiateByClassName(OptionHelper.java:47) at at ch.qos.logback.core.util.OptionHelper.instantiateByClassName(OptionHelper.java:31) at at ch.qos.logback.core.pattern.parser.Compiler.createConverter(Compiler.java:101) at at ch.qos.logback.core.pattern.parser.Compiler.compile(Compiler.java:58) at at ch.qos.logback.core.pattern.parser.Parser.compile(Parser.java:66) at at ch.qos.logback.core.pattern.PatternLayoutBase.start(PatternLayoutBase.java:84) at at ch.qos.logback.classic.net.SMTPAppender.makeSubjectLayout(SMTPAppender.java:101) at at ch.qos.logback.core.net.SMTPAppenderBase.start(SMTPAppenderBase.java:155) at at ch.qos.logback.classic.net.SMTPAppender.start(SMTPAppender.java:60) at at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96) at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315) at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194) at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180) at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52) at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52) at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77) at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150) at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85) at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55) at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121) at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111) at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254) at at com.siemens.ad.ld.listener.DataSourceService.<clinit>(DataSourceService.java:37) at at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at at java.lang.Class.newInstance0(Class.java:359) at at java.lang.Class.newInstance(Class.java:312) at at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4079) at at org.apache.catalina.core.StandardContext.start(StandardContext.java:4630) at at org.apache.catalina.core.StandardContext.reload(StandardContext.java:3391) at at org.apache.catalina.manager.ManagerServlet.reload(ManagerServlet.java:943) at at org.apache.catalina.manager.HTMLManagerServlet.reload(HTMLManagerServlet.java:556) at at org.apache.catalina.manager.HTMLManagerServlet.doGet(HTMLManagerServlet.java:121) at at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:563) at at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:861) at at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:579) at at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1584) at at java.lang.Thread.run(Thread.java:619) 15:13:57,525 |-ERROR in ch.qos.logback.core.pattern.parser.Compiler@1a54421 - [cn] is not a valid conversion word 15:13:57,532 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] {noformat} %contextName does work. This is a bug -- 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

[JIRA] Created: (LBCLASSIC-324) Allow specifying time zone in TimeBasedRollingPolicy's fileNamePattern
by William Ashley (JIRA) 21 Oct '12

21 Oct '12

Allow specifying time zone in TimeBasedRollingPolicy's fileNamePattern ---------------------------------------------------------------------- Key: LBCLASSIC-324 URL: http://jira.qos.ch/browse/LBCLASSIC-324 Project: logback-classic Issue Type: Improvement Components: appender Reporter: William Ashley Assignee: Logback dev list Priority: Minor I would like to have one of my application's logs use GMT for archive file names. The layout pattern currently supports specifying a time zone (documented under the conversion word 'd' http://logback.qos.ch/manual/layouts.html#conversionWord) but this is not supported when using the %d option with TimeBasedRollingPolicy (http://logback.qos.ch/manual/appenders.html#TimeBasedRollingPolicy) for file naming. -- 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-761) nlog4j-1.2.25 , use file buffer , lose some log
by zhang.haidi (JIRA) 14 Oct '12

14 Oct '12

2 2

[JIRA] Created: (LBCORE-247) SiftingAppender - Timeout for closing unused appenders should be configurable
by Tommy Becker (JIRA) 12 Oct '12

12 Oct '12

SiftingAppender - Timeout for closing unused appenders should be configurable ------------------------------------------------------------------------------ Key: LBCORE-247 URL: http://jira.qos.ch/browse/LBCORE-247 Project: logback-core Issue Type: Improvement Components: Appender Affects Versions: 1.0.0 Reporter: Tommy Becker Assignee: Logback dev list Priority: Minor We are using SiftingAppender to direct logs for each job in our application to a separate file. These files are typically only written to a few times in pretty quick succession and then they're done. While the appender works well, we have found that we are creating jobs at a faster rate than it closes the sub-appenders, causing us to eventually run out of file descriptors. I know about AppenderTracker and will implement a solution using this, but this feels like this timeout value is something that should be configurable on the SiftingAppender. Or maybe just some kind of boolean to tell it to close sub-appenders more aggressively. -- 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

1 1

[JIRA] (LOGBACK-759) NPE in SizeAndTimeBasedArchiveRemover
by Anders Wallgren (JIRA) 11 Oct '12

11 Oct '12

1 1

[JIRA] (LOGBACK-743) joranconfigurator fails if used in applet
by Gerhard Presser (JIRA) 11 Oct '12

11 Oct '12

1 1

Question about StackTrace Info
by Torsten Krah 10 Oct '12

10 Oct '12

Hi, i've got some jboss classloading problem and want to analyze this. Logback does output exception traces with the source of the loaded class and the version - e.g. hibernate-core.jar; 3.6.6. Can you tell me where in the logback source code (e.g. File, line number, code sample) this is done, so i can have a look at it? thx Torsten

2 1