[
https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-22376 at 11/29/16 6:40 PM:
--------------------------------------------------------------------
[~mlabuda] as stated
[
here|https://issues.jboss.org/browse/JBIDE-21857?focusedCommentId=1333105...]
jmx being connected isnt required for me to reproduce the simple case. What doesnt work
for you when HCR'ing if the JMX node in the Servers view isnt connected (it states
"[Disconnected]" without user connecting it manually)? I suspect the node not to
reflect whether jmx is being used or not when hot-code-replacing/debugging. I suspect it
to reflect if the MBeans are loaded.
[~rob.stryker] can you please chime in and provide the details?
was (Author: adietish):
[~mlabuda] as stated
[
here|https://issues.jboss.org/browse/JBIDE-21857?focusedCommentId=1333105...]
jmx being connected isnt required for me to reproduce the simple case. What doesnt work
for you when HCR'ing if the JMX node in the Servers view isnt connected (it states
"[Disconnected]" without user connecting it manually)?
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)