https://issues.apache.org/bugzilla/show_bug.cgi?id=51612
Curt Arnold <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #1 from Curt Arnold <[email protected]> 2011-08-08 03:18:17 UTC --- The code is behaving as designed, though it was designed for a far earlier era. Designing for concurrency is one of the prime motivations for the log4j 2 effort. Improving concurrency in log4j 1.x is a minefield with ample opportunity for unintended consequences. There are (at least were) substantial performance benefits to avoid copying thread state information into the logging event. The following fragment of AsyncAppender shows how it forces the retrieval of state information so that the logging event has a fixed state before it is made visible to other threads. event.getNDC(); event.getThreadName(); // Get a copy of this thread's MDC. event.getMDCCopy(); if (locationInfo) { event.getLocationInformation(); } event.getRenderedMessage(); event.getThrowableStrRep(); -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
