[jboss-jira] [JBoss JIRA] (REMJMX-160) Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed
Masafumi Miura (Jira)
issues at jboss.org
Fri May 10 07:36:00 EDT 2019
[ https://issues.jboss.org/browse/REMJMX-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Masafumi Miura updated REMJMX-160:
----------------------------------
Workaround Description:
- Reuse a JMXConnector object after it's created via JMXConnectorFactory#connect()
- Pass a custom executor to JMXConnectorFactory.connect(url, map) by passing the environment map with the key "java.util.concurrent.Executor"
was:
- Reuse a JMXConnector object after it's created via JMXConnectorFactory#connect()
- Pass a custom executor by the environment map with the key "java.util.concurrent.Executor"
> Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed
> --------------------------------------------------------------------------------------
>
> Key: REMJMX-160
> URL: https://issues.jboss.org/browse/REMJMX-160
> Project: Remoting JMX
> Issue Type: Bug
> Affects Versions: 1.1.3.Final, 3.0.1.Final
> Reporter: Masafumi Miura
> Assignee: JBoss SET
> Priority: Major
> Attachments: Memory.png, leaks.png
>
>
> In JMX client application, every JMXConnectorFactory#connect() invocation creates a new ThreadGroup which is never reclaimed.
> https://github.com/jbossas/remoting-jmx/blob/3.0.1.Final/src/main/java/org/jboss/remotingjmx/protocol/v2/ClientExecutorManager.java#L51
> If a JMX client application lives for long periods of time and repeats to invoke JMXConnectorFactory#connect() and JMXConnector#close(), a lot of ThreadGroup instances are retained eventually.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the jboss-jira
mailing list