> How could ConcurrentModificationExceptions occur? Log4j components do not > modify objects stored in the MDC. They but do not write... > Whatama-missing-here?
The issue is not log4j per se. The exception is a result of fail-fast iterators. If code in the main thread writes to MDC and a shallow copy is made and sent to the async appender and something in a chained, async appender is iterating over something in shared context while the main thread writes more to that context, the exception occurs. This is only an issue if you are iterating over something INSIDE MDC, not MDC itself. A bigger problem is actually that the asychronous logging will potentially log the WRONG data if the main thread changes context prior to it having an opportunity to logged the buffered event. -C --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
