[
https://issues.jboss.org/browse/JBIDE-12032?page=com.atlassian.jira.plugi...
]
Martin Malina resolved JBIDE-12032.
-----------------------------------
Resolution: Cannot Reproduce Bug
I cannot reproduce it now. I clearly saw the errors, but not sure how that happened. Now
it seems to work as expected.
JMX connection to remote AS7 not working even with -Dmanagement set
up
----------------------------------------------------------------------
Key: JBIDE-12032
URL:
https://issues.jboss.org/browse/JBIDE-12032
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.CR1
Environment: jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar
Reporter: Martin Malina
Assignee: Martin Malina
Priority: Critical
Fix For: 3.3.0.CR1
JMX connection to remote AS7 server is broken again :(
It may have to do with JBIDE-11921 or JBIDE-12028.
When you start a remote AS7 server with both "Listen on all interfaces" and
"Expose your management port" checked and then try to expand the server in MBean
Explorer, it displays "Loading" for a while and then errors with:
{code}
!ENTRY org.jboss.ide.eclipse.as.core 4 0 2012-05-28 13:25:21.013
!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 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:105)
at org.jboss.tools.jmx.core.tree.NodeUtils.createObjectNameTree(NodeUtils.java:51)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.loadRoot(JBossServerConnection.java:87)
at
org.jboss.tools.jmx.ui.internal.views.navigator.MBeanExplorerContentProvider$1.run(MBeanExplorerContentProvider.java:110)
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.connect(RemotingConnector.java:154)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
at
org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67)
... 7 more
!SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2012-05-28 13:25:21.014
!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.connect(RemotingConnector.java:154)
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:105)
at org.jboss.tools.jmx.core.tree.NodeUtils.createObjectNameTree(NodeUtils.java:51)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.loadRoot(JBossServerConnection.java:87)
at
org.jboss.tools.jmx.ui.internal.views.navigator.MBeanExplorerContentProvider$1.run(MBeanExplorerContentProvider.java:110)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
(Yes, two errors - perhaps for the two intended connections?)
Also, the start poller was set to Web Poller, as the default JBoss 7 Manager Service
currently doesn't work due to JBIDE-12028
--
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