[
https://issues.apache.org/jira/browse/LOG4J2-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832910#comment-16832910
]
Remko Popma commented on LOG4J2-2576:
-------------------------------------
Will you be able to provide a patch or pull request to improve this?
> 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.8.2, 2.11.2
> Reporter: Nicholas Wertzberger
> Priority: Minor
>
> Tried on at least 2.8.2 and 2.11.2, the jmx mbeans normally available
> disappear if using log4j2 as the JCL logging manager. Is this on purpose?
> Does it have to be this way? Using the java.util.logging mbeans for
> "setLoggerLevel" don't appear to work on log4j2 loggers, either.
>
> To recreate, start up any app with log4j2 logging, specifying
> -Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager as a
> system property.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
