You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Nicholas Wertzberger (JIRA)" <ji...@apache.org> on 2019/03/26 21:37:00 UTC

[jira] [Created] (LOG4J2-2576) JMX MBeans go away if using -Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager

Nicholas Wertzberger created LOG4J2-2576:
--------------------------------------------

             Summary: JMX MBeans go away if using -Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager
                 Key: LOG4J2-2576
                 URL: https://issues.apache.org/jira/browse/LOG4J2-2576
             Project: Log4j 2
          Issue Type: Bug
    Affects Versions: 2.11.2, 2.8.2
            Reporter: Nicholas Wertzberger


Tried on at least 2.8.2 and 2.11.2, the jmx mbeans normally available disappear if usinglog4j2 as the JCL logging manager. Is this on purpose? Does it have to be this way? I would prefer to use your mbeans.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)