[
https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-19463:
---------------------------------------
[~rob.stryker], thanks for all the explanations. Now I get that it's probably not
feasible to add all the client jars. And I'm not really sure if adding the option for
users to add their client jar would help - if they have the jar, they likely have the
whole server on the disk, so why not create the runtime and then it works?
So again, I think it would be good to warn users about this somewhere - as I suggested in
one of my previous comments.
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)