[jboss-jira] [JBoss JIRA] (REMJMX-95) RemotingConnector violates JMXConnector#connect contract and leads to thread explosion

Sergiy Barlabanov (JIRA) issues at jboss.org
Mon Mar 16 11:35:19 EDT 2015


Sergiy Barlabanov created REMJMX-95:
---------------------------------------

             Summary: RemotingConnector violates JMXConnector#connect contract and leads to thread explosion
                 Key: REMJMX-95
                 URL: https://issues.jboss.org/browse/REMJMX-95
             Project: Remoting JMX
          Issue Type: Feature Request
          Components: Connection
    Affects Versions: 2.0.0.Final
         Environment: Wildfly 8.2.0
            Reporter: Sergiy Barlabanov
            Assignee: Darran Lofthouse


The javadoc of javax.management.remote.JMXConnector#connect says that "If connect has already been called successfully on this object, calling it again has no effect.".
But this does not work with org.jboss.remotingjmx.RemotingConnector. Every connect result in a creation of a remoting endpoint with the corresponding io/worker threads, which are not closed when close() method is called. Only the threads from the first connect() invocation are closed, all threads created from the subsequent connect() invocations are not closed and stay alive until the VM shutdown.
Our application currently crashes after 10 minutes running - it pulls some JMX data periodically and after some time, the VM refuses to create new threads.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)


More information about the jboss-jira mailing list