http://bugzilla.qos.ch/show_bug.cgi?id=99 ------- Comment #2 from joern@huxhorn.de 2007-09-26 12:30 ------- Hi Ceki. I'm really confused myself because I already compared 0.9.7 vs 0.9.8 and couldn't find any changes that look critical. My only guess (and it's just that - a guess) is that there may be a problem in LogbackMDCAdapter or StaticMDCBinder because those files are actually new. There's also a change in LoggingEvent concerning MDC so this could really (somehow) be the reason. The whole problem does not manifest if I'm only using logback for logging (like in my test-application for my viewer) without any third-party jars that use log4j and/or commons-logging so it's probably a problem connected to static logger instances in those third-party jars. The Log-Event-Receiver is my own application which you can download at http://lumberjack.huxhorn.de/lumberjack0914.zip (it's not yet released "in the wild" but I welcome any comments). My viewer is using 0.9.8 in both cases, i.e. it's working with 0.9.7 in the application sending the logging events and does not work (drops and recreates connections while losing events) with 0.9.8. I double and triple-checked this... it's *really* reproducible by just changing the logback-dependencies from 0.9.7 to 0.9.8 in the application that's sending the log-events. The problem manifests in both our web-application and our console application so I can at least say that it's not a web-container-related problem. Both apps use spring-framework during startup which in turn uses commons-logging. We are also depending on spring-modules-cache-0.7 which depends on log4j. I'm sorry about this rather obscure problem and will try to isolate it further... -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.