[
https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-19463.
---------------------------------
Resolution: Rejected
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection has the following code:
{code}
public boolean canControl() {
return server.getServerState() == IServer.STATE_STARTED && server.getRuntime()
!= null;
}
{code}
This behavior is correct. With no runtime, we cannot add jars to our running classpath to
actually open up a proper JMX connection. We need a local runtime from which to load the
required client jars for our JMX calls.
Cannot connect to remote server in JMX Navigator
------------------------------------------------
Key: JBIDE-19463
URL:
https://issues.jboss.org/browse/JBIDE-19463
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.2.3.CR1, 4.3.0.Alpha1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.3.0.Beta1
When you start a remote EAP 6.3 server with management enabled and set up and then want
to connect in JMX Navigator, it does not work - double clicking the connection will not do
anything and when you right-click, there is no Connect item.
For local servers this works fine - there is a Connect item when you right-click the
server in JMX Navigator.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)