[arquillian-issues] [JBoss JIRA] (ARQ-632) org.jboss.arquillian.container.spi.client.protocol.metadata.JMXContext should close the JMXConnector when use of MBeanServerConnection is complete

[Aslak Knutsen (Assigned) (JIRA)]

     [ https://issues.jboss.org/browse/ARQ-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aslak Knutsen reassigned ARQ-632:
---------------------------------

    Assignee: Tommy Tynjä

    
> org.jboss.arquillian.container.spi.client.protocol.metadata.JMXContext should close the JMXConnector when use of MBeanServerConnection is complete
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARQ-632
>                 URL: https://issues.jboss.org/browse/ARQ-632
>             Project: Arquillian
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.0.0.CR5
>            Reporter: Scott Marlow
>            Assignee: Tommy Tynjä
>            Priority: Critical
>             Fix For: 1.0.0.Final
>
>
> The AS7 testsuite started experiencing "JMX server connection timeout 552" threads accumulating during the AS7 testsuite run.  If the testsuite runs fast enough, this seems to cause "OutOfMemoryError: unable to create new native thread" errors near the end of the testsuite run.  
> This doesn't recreate for everyone but it does for me.
> To fix this, I think we need to keep the JMXConnector returned from calling JMXConnectorFactory.connect() until we are done with the MBeanServerConnection and call JMXConnector.close() then.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira