ory. So I am wondering if maybe the status logger is behaving differently
than it should because of this set up.
>
> From: Mitchell Rathbun (BLOOMBERG/ 731 LEX) At: 05/26/20 20:11:23
> To: log4j-user@logging.apache.org <mailto:log4j-user@logging.apache.org>
> Subject: Re: Concu
uded with storm-core (which is 2.8.2, not 2.13.2). Not sure if this is
> the right place for this issue
>
> From: log4j-user@logging.apache.org At: 05/23/20 20:27:18
> To: Mitchell Rathbun (BLOOMBERG/ 731 LEX )
> <mailto:mrathb...@bloomberg.net>, log4j-user@logging.apache.
-user@logging.apache.org
Subject: Re: ConcurrentModificationException when using AsyncLogger
The first thing that I wanted to look at is why 2.13.2 is not being used. We
are using apache-storm, through which our project has the maven dependency
storm-core with a provided scope. Storm-core has depende
@logging.apache.org At: 05/23/20 20:27:18To: Mitchell Rathbun
(BLOOMBERG/ 731 LEX ) , log4j-user@logging.apache.org
Subject: Re: ConcurrentModificationException when using AsyncLogger
This stack trace is not from Log4j 2.13.2. The line numbers don’t match. This
error indicates that one of the parameters
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
