What's weird is we haven't changed our version of logback or slf4j in quite some time.  We're using logback 0.9.28 and slf4j 1.6.1

On Mon, Aug 13, 2012 at 11:27 AM, ceki <ceki@qos.ch> wrote:

Hi Robert,

What happens when you revert to the previous versions of logback? Which versions are we talking about?
--
Ceki
http://tinyurl.com/proLogback


On 13.08.2012 18:09, Robert Voliva wrote:
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?


_______________________________________________
Logback-user mailing list
Logback-user@qos.ch
http://mailman.qos.ch/mailman/listinfo/logback-user