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

Posted to notifications@logging.apache.org by "edgar wang (JIRA)" <ji...@apache.org> on 2018/01/24 02:29:00 UTC

[jira] [Created] (LOG4J2-2216) JMXFactoryConnector is not closed in ClientGui

edgar wang created LOG4J2-2216:
----------------------------------

             Summary: 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.8, 2.6
            Reporter: edgar wang


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)