[
https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-22376:
------------------------------------------
[~mlabuda] yes I can confirm this. You need the server adapter to be in Debug mode and you
have to create a structural change (that is not hot code replaceable with default means)
so that JMX gets connected. But once you have these 2 conditions met, JMX is connected
automatically. Resolving, Re-closing as discussed.
Enable JMX when entering Debug mode
-----------------------------------
Key: JBIDE-22376
URL:
https://issues.jboss.org/browse/JBIDE-22376
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: jmx, openshift
Affects Versions: 4.1.1.Beta1
Reporter: Thomas Mäder
Assignee: Rob Stryker
Fix For: 4.4.2.Final
We need to update the deployment configuration when entering debug mode. It is not
entirely clear how to determine that an Openshift Pod has indeed a wildfly/EAP in it and
can be reached with remoting-jmx
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)