[
https://issues.apache.org/jira/browse/LOG4J2-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16338405#comment-16338405
]
Remko Popma commented on LOG4J2-2216:
-------------------------------------
Have you tried running your application with system property
{{log4j2.disableJmx}} set to {{true}} to see if the leak still occurs? That
would exclude Log4j2 as the source of the 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)
