[ https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi... ] 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? -- This message was sent by Atlassian JIRA (v7.2.3#72005)