We do almost the exact same thing Chris. I have verified that with only 0.9.24 in each app's lib folder, it still has this behavior. So with Chris' input, it looks like this problem is confirmed to happen in 0.9.24, 0.9.28, and 1.0.6 - On Thu, Aug 16, 2012 at 11:01 AM, Chris Rompot <crompot@gmail.com> wrote:
Ceki Gulcu wrote:
If my memory serves me correctly, the context selection code has not changed significantly since 0.9.28.
How do you perform context selection? Is it JNDI based? Again, what happens when you revert to logback 0.9.28?
-- Ceki http://tinyurl.com/proLogback
We recently noticed the same problem using logback-classic version 1.0.6. We store our LoggerContexts as values of a static HashMap. I have verified that the keys used to retrieve the appropriate LoggerContext have distinct hash codes. In the example that we noticed, the appropriate context was used on 2012-08-15 11:48:58 - 15:48:07 after which it was no longer used. Log entries that should have gone to it were mixed in with those for a newly created context from 2012-08-15 15:48:28 on.
-- View this message in context: http://old.nabble.com/Logging-crossing-contexts-tp34292668p34307440.html Sent from the Logback User mailing list archive at Nabble.com.
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user