[
https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-11064:
---------------------------------------
OK, you're right, JMX connection to AS7.1 does not work. But why isn't there an
error at the startup? Do we expect it not to work and so we don't even try?
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.CR1
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