[
https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi...
]
Isaac Rooskov updated JBIDE-11064:
----------------------------------
Release Notes Text:
Only customers who downloaded and used the Beta release of JBoss Developer Studio 5 may
have noticed this issue, that has since been resolved.
The JBoss Developer Studio 5.0.Beta JMX tooling was unable to connect to JBoss Application
Server 7.1.0 correctly as the ability to connect to the new connector and URL for the
server had not been incorporated. New classes have been created for interaction between
JMX and JBoss Application Server 7.1.0 and are available as part of JBoss Developer Studio
5.0.
was:
Only customers who downloaded and used the Beta release of JBoss Developer Studio 5 may
have noticed this issue, that has since been resolved.
The JBoss Developer Studio 5.0.Beta JMX tooling was unable to connect to JBoss Application
Server 7.1.0 correctly as the ability to connect to the new connector and URL for the
server had not been incorporated. New classes have been created for interaction between
JMX and JBoss Application Server 7.1.0 and area available as part of JBoss Developer
Studio 5.0.
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, jmx
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
Priority: Blocker
Labels: new_and_noteworthy
Fix For: 3.3.0.Beta3
Attachments: as7.0.2remote.log, JBIDE-11064.v10.patch, JBIDE-11064.v11.patch,
jbide-11064_branch.patch
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