[jbosstools-issues] [JBoss JIRA] (JBIDE-12109) JMX connection to AS7/EAP6 not working if server started with Java 1.7

Martin Malina (JIRA) jira-events at lists.jboss.org
Wed Jun 6 06:50:17 EDT 2012


     [ https://issues.jboss.org/browse/JBIDE-12109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Malina updated JBIDE-12109:
----------------------------------

    Environment: 
jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar
Mac OS X 10.7 Lion

  was:jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar



It seems this only affects Java 1.7 on Mac - rawagner just tried it on Ubuntu and it works for him.
                
> JMX connection to AS7/EAP6 not working if server started with Java 1.7
> ----------------------------------------------------------------------
>
>                 Key: JBIDE-12109
>                 URL: https://issues.jboss.org/browse/JBIDE-12109
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 3.3.0.CR1
>         Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar
> Mac OS X 10.7 Lion
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 3.3.1
>
>
> 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:
> {code}
> !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)
> {code}
> 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.

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

        


More information about the jbosstools-issues mailing list