[
https://issues.apache.org/jira/browse/LOG4J2-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16338113#comment-16338113
]
Ralph Goers edited comment on LOG4J2-2216 at 1/24/18 7:40 PM:
--------------------------------------------------------------
What do you mean "clientgui is enabled by default"? It is a separate
application with a main method. According to
http://logging.apache.org/log4j/2.x/manual/jmx.html it can be run standalone or
as a JConsole plugin, but it is not part of a web application.
Also, as I said in my previous reply, if you are using a class named
JMXFactoryConnector then it is a class that isn't part of Log4j or the JDK. The
JDK class is JMXConnectorFactory.
was (Author: [email protected]):
What do you mean "clientgui is enabled by default"? It is a separate
application with a main method. According to
http://logging.apache.org/log4j/2.x/manual/jmx.html it can be run standalone or
as a JConsole plugin, but it is not part of a web application.
> JMXFactoryConnector is not closed in ClientGui
> ----------------------------------------------
>
> Key: LOG4J2-2216
> URL: https://issues.apache.org/jira/browse/LOG4J2-2216
> Project: Log4j 2
> Issue Type: Bug
> Components: JMX
> Affects Versions: 2.6, 2.8
> Reporter: edgar wang
> Priority: Minor
>
> JMXFactoryConnector is not closed in ClientGui. This potentially could cause
> a thread leak according to
> [https://stackoverflow.com/questions/564589/dynamic-proxies-with-jmx-can-cause-thread-leaks]
> . Since JMXFactoryConnector implements closable and autoclosable, it should
> be wrapped in a try with resources or the connector should be closed
> somewhere.
> We've seen several unclosed JMX threads in our production environment and
> believe this could be a reason why.
> Could anyone advise?
> Thanks!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
