Details
-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
3.3.0.CR1
-
None
Description
When you set up your AS7/EAP6 server to use Java 1.7 runtime, the tooling fails to connect to the server via JMX. The error in the log is:
!ENTRY org.jboss.ide.eclipse.as.jmx.integration 4 0 2012-06-06 12:17:52.897
!MESSAGE Error connecting to jmx for server jboss-eap-6.0.0.CR1
!STACK 1
org.jboss.tools.jmx.core.JMXException: Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property
at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:78)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:111)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:221)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:213)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.RuntimeException: Operation failed with status WAITING
at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:168)
at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67)
... 6 more
!SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2012-06-06 12:17:52.897
!MESSAGE Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property
!STACK 0
java.lang.RuntimeException: Operation failed with status WAITING
at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:168)
at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:111)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:221)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:213)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
This has several consequences:
- server cannot be connected in MBean Explorer
- management startup poller does not work and hence the server keeps starting forever until it reaches timeout (and then it tries to stop the server, but fails to do so - see below)
- server fails to stop because it seems it tries to do so using management service, second attempt kills the process successfully
Unfortunately I didn't catch this earlier. AS7/EAP6 with Java 1.7 worked for me in JBDS in the past, but that was probably before the jmx connection started working correctly at all.
