[logback-user] Logging crossing contexts

[Thorbjørn Ravn Andersen]

Have you upgraded any other components, like Mule itself?

 

If yes, then Mule might be accidentally be polluting your classpath with
another implementation of a component you use so the two contexts suddenly
can “see” one another.

 

You may want to do some investigations on what jars are available on your
context classpath.  A simple snippet searching for all MANIFEST.MF resources
and then ask where it is located should allow you to get a list.

 

/Thorbjørn

 

From: logback-user-bounces at qos.ch [mailto:logback-user-bounces at qos.ch] On
Behalf Of Robert Voliva
Sent: 13. august 2012 18:09
To: logback-user at qos.ch
Subject: [logback-user] Logging crossing contexts

 

We run multiple apps in the same instance of Mule (ESB product), all in the
same JVM.  We use a context selector to setup each app with its own logging
context at startup.  This has worked fine for quite some time, we haven't
upgraded/changed any slf4j or logback dependencies, and it suddenly stopped
working.  What's happening now is that we're getting parts of our logging
ending up in other context's log files.  

 

For example, we'll get a WARN message in the appropriate log file, but then
a stack trace for that app will get logged to a different context's log
file.  It ends up in the same log file every time we restart, so it seems to
be repeatable.  Even if we remove all but two apps from the JVM, we can show
that even with just those two apps they log to each other's log files.

 

Any ideas out there for me to try?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-user/attachments/20120814/0be90024/attachment-0001.html>