Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-2216

JMXFactoryConnector is not closed in ClientGui

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • 2.6, 2.8
    • None
    • JMX
    • None

    Description

      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!

      Attachments

        Activity

          People

            Unassigned Unassigned
            wanedgar edgar wang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: