[jbosstools-issues] [JBoss JIRA] (JBIDE-11872) Auto-connection to jmx after rse server start leaves threads hanging around

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-11872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693122#comment-12693122 ] 

Rob Stryker commented on JBIDE-11872:
-------------------------------------

POJP tests show simply adding the proper remoting to the cp before the other does use the proper remoting, however, POJP test does not replicate issue as of yet ;)  will test a bit more. 
                
> Auto-connection to jmx after rse server start leaves threads hanging around
> ---------------------------------------------------------------------------
>
>                 Key: JBIDE-11872
>                 URL: https://issues.jboss.org/browse/JBIDE-11872
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 3.3.0.Beta3
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 3.3.0.CR1
>
>
> Because of the way the as7.1 mbean connector loads the client jar direct from the server installation, the auto-connection to jmx does not benefit from the remoting upgrade committed by JBIDE-11871. The client jar for a 7.1.0 installation, for example, will still use remoting 3.2.2 rather than the astools-bundled 3.2.7.  
> Possible solutions are prevent auto-connection of jmx or somehow force the 3.2.7 remoting jar onto the classpath before the as7.1.0 client jar to ensure 3.2.7 classes take precedence. 

--
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