[
https://issues.apache.org/jira/browse/LOG4J2-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16338172#comment-16338172
]
edgar wang commented on LOG4J2-2216:
------------------------------------
whoops I meant JMX was enabled by default. I didn't realize that it was a
standalone application and assumed it was always on as part of the log4j to
enable remote debugging.
in the client gui, there's
final JMXConnector connector = JMXConnectorFactory.connect(url, paramMap); so
that's the JMXConnectorFactory I was referring to. To clarify, we're not using
it directly but throught log4j
Looking more into it, to the best of my knowledge no one on my team uses the
clientgui so it is unlikely that this is the cause of our leaks.
> 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)
