[
https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-19463:
-------------------------------------
Anything else?
Autodetection of ports by scanning your standalone.xml (or your selected configuration
file). Since there's no local runtime, and no local standalone.xml, we can't
notice that you've modified your ports to be non-standard.
Also, without a local runtime, *some* small behavior changes might be default values. For
example, sometimes we hard-code different behavior between minor or micro versions if we
notice there's a bug in some previous release. For example, some of the early jboss-7
releases didn't support the -b flag.
Without a local runtime to scan, we can't know the *exact* version you're running
against, and can't customize args (or other things) to work around bugs in those
specific runtime versions.
Cannot connect to remote server without runtime 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.Beta2
Attachments: jmx-text.png
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)