[
https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi...
]
Marián Labuda edited comment on JBIDE-22376 at 12/1/16 6:23 AM:
----------------------------------------------------------------
Ok, after further investigation JMX is not enabled by default when entering debug mode on
OpenShift Server adapter. It gets connected but it needs few seconds after restarting of a
module (prompt shown if HCR incompatible change has been done). If this is intended and it
is the issue this JIRA is targeting, please confirm and we can close this one.
was (Author: mlabuda):
Ok, after further investigation JMX is not enabled by default when entering debug mode on
OpenShift Server adapter. It gets connected few seconds after restarting of a module if
HCR incompatible change has been done. If this is intended and it is the issue this JIRA
is targeting, please confirm and we can close this one.
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, 4.4.3.AM1, 4.5.0.AM1
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)