OK, I had forgotten about this issue. It was closed quite a while ago. It
indicates the issue was fixed in 2.9.1 so upgrading should fix it.
Apache mailing lists generally strip attachments so I can’t view your
configuration. If log4j2.debug is set to true StatusLogger writes all status
events
The main reason that I mentioned the version was due to the issue:
https://issues.apache.org/jira/browse/LOG4J2-1988. There are multiple comments
here that seem to indicate that this exception should never happen with an
AsyncLogger since some sort of copy is made when the logging method is call
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 dependencies on log4j-api,
log4j-core, and log4j-slf4j-impl. It seems like these have provided
