- logback-dev - mailman3.qos.ch

[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

[qos-ch/logback] 14e4d8: minor edit
by Ceki Gulcu 17 Sep '12

17 Sep '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 14e4d89c450f1f987f3d550bca3e38947ed3d4c9 https://github.com/qos-ch/logback/commit/14e4d89c450f1f987f3d550bca3e38947e… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-09-17 (Mon, 17 Sep 2012) Changed paths: M logback-site/src/site/pages/manual/configuration.html Log Message: ----------- minor edit

1 0

Logback config access and fallback
by Ravi Kumar 14 Sep '12

14 Sep '12

Hi, I am new to Logback, and actually I am a Core Python Dev. I want to implement mongodb logging in logback, and all existing solutions (even one included in logback extra) does not handle connection problem gracefully. There for implementing such features, I am trying to find - 1. How the config that is defined in logback.xml (or logback-test) is accessed in my appender. 2. Will I be able to define my own configs or do i have to stick to given configs. 3. When connecting mongodb or inserting, sometimes when server is down, I need to handle it. In case of such failure, I want to store that log in another file or maybe if possible I would like to redirect the message/Log to another appender. How can I do it? I would really appreciate if I get some pointers or help. I tried to search google for these these queries, but couldn't find something easy to understand. :( Thanks, Ravi

1 0

remove EclipseLogAppender?
by Tony Trinh 11 Sep '12

11 Sep '12

Now that we have logback-beagle [1], I think the EclipseLogAppender [2] is obsolete and not as useful. Does anyone object to having it removed from logback-extensions? [1]: https://github.com/qos-ch/logback-beagle [2]: https://github.com/qos-ch/logback-extensions/tree/master/eclipse Tony

3 2

[JIRA] (CONSPLUG-37) License is messed up in Install dialog
by Daniel Serodio (JIRA) 11 Sep '12

11 Sep '12

1 0

[qos-ch/logback] 5a9c5b: upgrade to slf4j 1.7.0, added list of CLAs on file
by Ceki Gulcu 11 Sep '12

11 Sep '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 5a9c5bd99810e648624b65ca3a9385a7e9bee3c3 https://github.com/qos-ch/logback/commit/5a9c5bd99810e648624b65ca3a9385a7e9… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-09-11 (Tue, 11 Sep 2012) Changed paths: M pom.xml A src/main/clas/signed-clas.txt Log Message: ----------- upgrade to slf4j 1.7.0, added list of CLAs on file

1 0