[jbosstools-issues] [JBoss JIRA] (JBIDE-22376) Enable JMX when entering Debug mode
Marián Labuda (JIRA)
issues at jboss.org
Thu Nov 24 09:12:01 EST 2016
[ https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13327652#comment-13327652 ]
Marián Labuda edited comment on JBIDE-22376 at 11/24/16 9:11 AM:
-----------------------------------------------------------------
What has been done there precisely? So i can verify its working as expected. I compared DC of a new application and a deployment config of application in debugging. There is a new port for debug 8787, but what with latest changes to EAP images the jolokia port is 8787 so basically we have 2 same ports with a different name, I don't think it is necessary. Then there are added environment variables:
{code}
{
"name" : "DEBUG_PORT",
"value" : "8787"
},
{
"name" : "DEV_MODE",
"value" : "true"
},
{
"name" : "DEBUG",
"value" : "true"
}
{code}
was (Author: mlabuda):
What has been done there precisely? So i can verify its working as expected. I compared DC of a new application and a deployment config of application in debugging. There is a new port for debug 8787, but what with latest changes to EAP images the jolokia port is 8787 so basically we have 2 same ports with a different name, I don't think it is necessary. Then there are added environment variables:
{code}
{
"name" : "DEBUG_PORT",
"value" : "8787"
},
{
"name" : "DEV_MODE",
"value" : "true"
},
{
"name" : "DEBUG",
"value" : "true"
}
{code}
DEV_MOVE env var was added by mistake probably bcs. of nodejs debugging. It is not required for EAP debugging AFAIK. With DEBUG and DEBUG_PORT env vars. I am not sure, should those be there?
> 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)
More information about the jbosstools-issues
mailing list