[jbosstools-issues] [JBoss JIRA] (JBIDE-19463) Cannot connect to remote server in JMX Navigator
Rob Stryker (JIRA)
issues at jboss.org
Mon Jun 1 14:52:02 EDT 2015
[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072861#comment-13072861 ]
Rob Stryker commented on JBIDE-19463:
-------------------------------------
Connecting to local (or remote) jmx loads jars from the LOCAL runtime installation into a ClassLoader for the purposes of executing the remote jmx commands.
This differs from our management plugins, which bundle all deps (remoting, dmr, threads, etc) for each breaking version in the server.
The request here is to connect to a remote server for JMX while NOT having a local jboss-as / wildfly from which to pull JMX classes / jars. This would require bundling more libs (jboss-client-all.jar) for each different app server. This will balloon the size of our deps, and probably require new plugins. (We currently have a management.71 and management.80... now imagine adding new plugins for jmx for every app server version in the past, which requires jboss-client-all.jar for each breaking version).
> 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)
More information about the jbosstools-issues
mailing list