September 2012 - logback-dev

[JIRA] (LOGBACK-752) Content overflow under TOC box
by Libor Jelinek (JIRA) 27 Sep '12

27 Sep '12

1 0

[JIRA] (LOGBACK-745) TimeBasedRollingPolicy does not trigger
by Tomas Jetelina (JIRA) 27 Sep '12

27 Sep '12

1 2

[JIRA] Created: (LBCORE-228) Syslog messages over 64K are discarded
by Pasi Eronen (JIRA) 25 Sep '12

25 Sep '12

Syslog messages over 64K are discarded -------------------------------------- Key: LBCORE-228 URL: http://jira.qos.ch/browse/LBCORE-228 Project: logback-core Issue Type: Bug Components: Appender Affects Versions: 0.9.30 Reporter: Pasi Eronen Assignee: Logback dev list SyslogAppenderBase truncates very long messages to 256k, which is not very useful limit, since SyslogOutputStream supports only UDP, which has maximum message size of 64k. Messages over 64k result in "java.io.IOException: Message too long" (from DatagramSocket.send, called from SyslogOutputStream.flush), but this exception is visible only in logger context status... Proposed fix: truncate long messages instead of discarding them. More specifically, change MSG_SIZE_LIMIT in SyslogAppenderBase to 65000. -- 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-319) SyslogAppender prints %PARSER_ERROR[nopexXXX] when suffixPattern doesn't start with [
by Markus Binsteiner (JIRA) 25 Sep '12

25 Sep '12

SyslogAppender prints %PARSER_ERROR[nopexXXX] when suffixPattern doesn't start with [ ------------------------------------------------------------------------------------- Key: LBCLASSIC-319 URL: http://jira.qos.ch/browse/LBCLASSIC-319 Project: logback-classic Issue Type: Bug Affects Versions: 0.9.30, 1.0.0 Reporter: Markus Binsteiner Assignee: Logback dev list Priority: Minor When I use the SyslogAppender and specify a suffixPattern that starts with a whitespace or other character that is not [ logback seems to just append the string (until the first occurence of certain characters, e.g -) to the internal "%nopex" string. Subsequently it fails to parse the %nopexXXX string and prints something like: Jan 12 15:54:14 think %PARSER_ERROR[nopexXXX] [main] LogTest DEBUG FROM JAVA... to syslog. Had a look in the sourcecode, but couldn't figure out where it goes wrong, but I could confirm that if I add a whitespace to the string in this line String prefixPattern = "%syslogStart{" + facilityStr + "}%nopex "; there is no PARSER_ERROR. An additional whitespace in the logmessage though (I can live with that though). I need to be able to specify a string that doesn't start with [ though for some crazy reason (almost funny -- every other character would have been ok as far as I could figure out...). Any chance that could be looked into and included in one of the next releases? Thanks in advance... -- 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] 748b84: added setMDCPropertyMap
by Ceki Gulcu 25 Sep '12

25 Sep '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 748b8445fe8075d34b292fe1e1f364dfb3aaad03 https://github.com/qos-ch/logback/commit/748b8445fe8075d34b292fe1e1f364dfb3… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-09-25 (Tue, 25 Sep 2012) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggingEvent.java Log Message: ----------- added setMDCPropertyMap

1 0

[JIRA] Created: (LBCORE-248) Logback Context is not thread safe, throws java.util.ConcurrentModificationException
by Svetla Arnaudova (JIRA) 22 Sep '12

22 Sep '12

Logback Context is not thread safe, throws java.util.ConcurrentModificationException ------------------------------------------------------------------------------------- Key: LBCORE-248 URL: http://jira.qos.ch/browse/LBCORE-248 Project: logback-core Issue Type: Bug Affects Versions: 1.0.0 Environment: Windows 7 OS, Java 1.6 build 1.6.0_27-b07, Tomcat 7 Reporter: Svetla Arnaudova Assignee: Logback dev list We see the following exception in Status messages for LoggerContext (see attached pic lbClassicStatus.jpg) java.util.ConcurrentModificationException at java.util.Hashtable$Enumerator.next(Hashtable.java:1031) at ch.qos.logback.classic.LoggerContext.syncRemoteView(LoggerContext.java:93) at ch.qos.logback.classic.LoggerContext.putProperty(LoggerContext.java:101) at ch.qos.logback.core.util.ContextUtil.addHostNameAsProperty(ContextUtil.java:42) at ch.qos.logback.classic.joran.action.ConfigurationAction.begin(ConfigurationAction.java:48) at ch.qos.logback.core.joran.spi.Interpreter.callBeginAction(Interpreter.java:276) at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:148) at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:130) at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:50) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:147) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:133) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:96) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:55) at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75) at com.excilys.ebi.utils.spring.log.logback.LogbackConfigurer.initLogging(LogbackConfigurer.java:90) at com.excilys.ebi.utils.spring.log.logback.web.LogbackWebConfigurer.initLogging(LogbackWebConfigurer.java:92) at com.excilys.ebi.utils.spring.log.logback.web.LogbackConfigListener.contextInitialized(LogbackConfigListener.java:43) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4723) at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5226) at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5221) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Our web application set default configuration logback.xml file in the class path so that logback will use it to configure itself during initialization. It is slightly different (only set info level) from the default basic configuration, used in case there is no such file (see attached logback.xml). The real logback.xml configuration file is outside of the web application (attached as logback-conf.xml) and we reconfigure logapp to use it with spring integration lib https://github.com/excilys/spring-log Not sure that the rest of the description will be helpful to troubleshoot the problem, but this is how we reproduce it: This is the example code: <context-param> <param-name>logbackConfigLocation</param-name> <param-value>file:${basedir}/conf/logback.xml</param-value> </context-param> <listener> <listener-class>com.excilys.ebi.utils.spring.log.logback.web.LogbackConfigListener</listener-class> </listener> After spring is loaded LogbackConfigListener class will initialize logback from the given location and reset the logger context. Code snip from LogbackConfigListener init logging below: public static void initLogging(String location) throws FileNotFoundException, JoranException { String resolvedLocation = SystemPropertyUtils.resolvePlaceholders(location); URL url = ResourceUtils.getURL(resolvedLocation); ContextSelector selector = ContextSelectorStaticBinder.getSingleton().getContextSelector(); LoggerContext loggerContext = selector.getLoggerContext(); // in the current version logback automatically configures at startup // the context, so we have to reset it loggerContext.reset(); ContextInitializer contextInitializer = new ContextInitializer(loggerContext); contextInitializer.configureByResource(url); // reset JUL // don't forget to configure the LevelChangePropagator contextListener // in the config file!!! SLF4JBridgeHandler.install(); } We sometimes receive concurrency modification exception from the logback core code. We never observe this issue if we remove default logback file from the class path as initial configuration. To prevent this exception we also delay logback configuration loading. Thank you, Svetla -- 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 4

[JIRA] (LOGBACK-718) Support Eclipse buddy policy for loading logback.xml
by Ceki Gulcu (JIRA) 19 Sep '12

19 Sep '12

7 10

[qos-ch/logback] be1455: fix typo
by Ceki Gulcu 19 Sep '12

19 Sep '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: be14553cb3584702f193205c1f306a6d73bdfe53 https://github.com/qos-ch/logback/commit/be14553cb3584702f193205c1f306a6d73… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-09-19 (Wed, 19 Sep 2012) Changed paths: M src/main/clas/signed-clas.txt Log Message: ----------- fix typo

1 0

[qos-ch/logback] f36631: added Matt Bishop
by Ceki Gulcu 19 Sep '12

19 Sep '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: f3663170615e343f5e99ebeb96f49afea81385f7 https://github.com/qos-ch/logback/commit/f3663170615e343f5e99ebeb96f49afea8… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-09-19 (Wed, 19 Sep 2012) Changed paths: M src/main/clas/signed-clas.txt Log Message: ----------- added Matt Bishop

1 0

[qos-ch/logback] d14c54: CLA for Libor Jelinek
by Ceki Gulcu 18 Sep '12

18 Sep '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: d14c54faa0347503c55be1e63954dd654aee551d https://github.com/qos-ch/logback/commit/d14c54faa0347503c55be1e63954dd654a… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-09-18 (Tue, 18 Sep 2012) Changed paths: M src/main/clas/signed-clas.txt Log Message: ----------- CLA for Libor Jelinek

1 0