Interesting bug reporting. I tried to reproduce the bug by specifying the system property (i.e. org.jboss.logging.provider) to both log4j and `log4j2