A second configuration is loaded and overwrites mine

Bean org.apache.logging.log4j2:type=/dk,component=Appenders,name=CONSOLEWARN DEBUG StatusLogger Registering MBean org.apache.logging.log4j2:type=/dk,component=Appenders,name=CONSOLEINFO DEBUG StatusLogger Registering MBean org.apache.logging.log4j2:type=/dk,component=Appenders,name=devnull TRACE StatusLogger Usin

Async logger context selector creates a throwable in JSON layout

Hello, I'm currently migrating our codebase to Log4j2 (2.9.1) in a Tomcat 9.0.7 environment, and while testing different configurations I noticed a weird, what i think also undocumented, difference between the standard usage and when starting with -DLog4jContextSelector=org.apa che.logging.log4j.co