[jbosstools-issues] [JBoss JIRA] (JBIDE-22376) Enable JMX when entering Debug mode

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13332079#comment-13332079 ] 

Andre Dietisheim commented on JBIDE-22376:
------------------------------------------

[~mlabuda] in https://issues.jboss.org/browse/JBIDE-21857?focusedCommentId=13331797&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13331797 I pasted my steps where I was not connecting JMX manually. I was doing incompatible changes, had the "Hot Code Replace Failed" dialog, which I told to restart the module, and once I checked the adapter again, JMX was connected (See screenshot). As far as I can see JMX is automatically connected once I do structural changes to a class. So imho this issue works. Do I miss something?

> 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)