[jbosstools-issues] [JBoss JIRA] (JBIDE-11064) JMX Connections to as7 errors out and is not usable at all.

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-11064:
-------------------------------------

Full implementation for as71 is being committed.  

There was a minor api change to jmx core (ability to run a jmx command and pass in some options) put in as a new method in the interface, so any consumers of this tool on an API level must beware. There was also additions to api. Some of the utility classes that help traverse nodes would create a new connection for each and every request.  If you were already within the scope of a connection, though, this was wasteful. This wasn't an issue for AS3-6, but in AS7.1 there are issues with threads staying around for a minute or more.  When traversing the entire jmx tree, this leads to an out of memory exception, so new API was added with an MBeanServerConnection parameter to help maintain the scope of the operation and prevent unnecessary creation of connections. 

So, it's all good now! 
                
> JMX Connections to as7 errors out and is not usable at all. 
> ------------------------------------------------------------
>
>                 Key: JBIDE-11064
>                 URL: https://issues.jboss.org/browse/JBIDE-11064
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 3.3.0.Beta1
>         Environment: jbdevstudio-product-universal-5.0.0.v201202250031M-H77-Beta1.jar
> JBoss AS 7.0.2
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 3.3.0.Beta3
>
>         Attachments: as7.0.2remote.log
>
>
> AS 7.0.2 fails to start using RSE.
> !ENTRY org.jboss.ide.eclipse.as.core 4 0 2012-02-27 11:26:24.651
> !MESSAGE Error connecting to this server's JMX service: jboss-as-7.0.2.Final on marvin
> !STACK 0
> java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException
> I'm not sure how exactly it works, but I am told that remote JNDI didn't really work in 7.0.2 so maybe that's why?

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