This stack trace is not from Log4j 2.13.2. The line numbers don’t match. This
error indicates that one of the parameters being passed on the logging method
is a Collection. The Layout is iterating over the Collection in an attempt to
format it. However, some other thread is modifying the Collec
Looks like one of the parameters to a log message is a HashMap which
gets modified while the log message was being constructed in another
thread. Using a synchronous appender would avoid the issue from
popping up since it's an issue of thread safety.
On Sat, 23 May 2020 at 17:46, Mitchell Rathbun
I just noticed this never got replied to. But I guess I need to add that I
don’t understand why you need to do this, or how you expect it to work. It
seems like you are trying to create a new Root Logger so you can add a custom
attribute to it. I’m not really sure why since that custom attribut
We recently started occasionally getting the following error:
2020-05-22 05:54:07,995 INFO STDERR [Thread-2] {} 2020-05-22 05:54:07,994
Log4j2-TF-2-AsyncLoggerConfig-1 ERROR An exception occurred processing Appender
WINGMAN java.util.ConcurrentModificationException
2020-05-22 05:54:07,996 INFO
