February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23961: ------------------------------------------ We should also fix the erroneous server adapter state, once debugging failed. > Server adapter: "Start/Restart in Debug" is broken for Nodejs > ------------------------------------------------------------- > > Key: JBIDE-23961 > URL: https://issues.jboss.org/browse/JBIDE-23961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Priority: Critical > Labels: respin-a > Attachments: image-2017-02-16-23-30-21-709.png, server-adapter-erroneous-debugging-state.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23961: ------------------------------------------ We should also fix the erroneous server adapter state, once debugging failed. > Server adapter: "Start/Restart in Debug" is broken for Nodejs > ------------------------------------------------------------- > > Key: JBIDE-23961 > URL: https://issues.jboss.org/browse/JBIDE-23961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Priority: Critical > Labels: respin-a > Attachments: image-2017-02-16-23-30-21-709.png, server-adapter-erroneous-debugging-state.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23961: ------------------------------------- Comment: was deleted (was: We should also fix the erroneous server adapter state, once debugging failed.) > Server adapter: "Start/Restart in Debug" is broken for Nodejs > ------------------------------------------------------------- > > Key: JBIDE-23961 > URL: https://issues.jboss.org/browse/JBIDE-23961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Priority: Critical > Labels: respin-a > Attachments: image-2017-02-16-23-30-21-709.png, server-adapter-erroneous-debugging-state.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23961: ------------------------------------------ I'm not fully sure but I couldnt experience the timeouts reported in JBIDE-23422 (cdk 2.4) > Server adapter: "Start/Restart in Debug" is broken for Nodejs > ------------------------------------------------------------- > > Key: JBIDE-23961 > URL: https://issues.jboss.org/browse/JBIDE-23961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Priority: Critical > Labels: respin-a > Attachments: image-2017-02-16-23-30-21-709.png, server-adapter-erroneous-debugging-state.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23961: ------------------------------------------ If freeze is already done, we should really do a respin for this critical issue I believe. > Server adapter: "Start/Restart in Debug" is broken for Nodejs > ------------------------------------------------------------- > > Key: JBIDE-23961 > URL: https://issues.jboss.org/browse/JBIDE-23961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Priority: Critical > Labels: respin-a > Attachments: image-2017-02-16-23-30-21-709.png, server-adapter-erroneous-debugging-state.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23961: ------------------------------------- Labels: respin-a (was: ) > Server adapter: "Start/Restart in Debug" is broken for Nodejs > ------------------------------------------------------------- > > Key: JBIDE-23961 > URL: https://issues.jboss.org/browse/JBIDE-23961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Priority: Critical > Labels: respin-a > Attachments: image-2017-02-16-23-30-21-709.png, server-adapter-erroneous-debugging-state.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23961 at 2/16/17 6:54 PM: ------------------------------------------------------------------- The cause for this is the following: In JBIDE-22362 we always enabled DEV_MODE for nodejs. When launching the debugger one finds the following code that checks if debugging is enabled: {code:title=OpenShiftDebugUtils#getDebuggingContext} debugContext.setDebugEnabled(Boolean.parseBoolean(debugEnabled) || Boolean.parseBoolean(devModeEnabled)); {code} Thus when a nodejs adapter starts the debugger it erroneously thinks that debugging is already active and wont reenable it. The following change *FIXES* it, the debugger is started correctly, no port error happens. {code} debugContext.setDebugEnabled(Boolean.parseBoolean(debugEnabled)); {code} But I'm very unsure about the side-effects. Maybe this now is only true for nodejs and will affect eap, too. We have to test this change throughoutly before applying it. [~fbricon] do you remember why debugging is considered enabled when dev_mode is enabled? was (Author: adietish): The cause for this is the following: In JBIDE-22362 we always enabled DEV_MODE. When launching the debugger one finds the following code that checks if the debugging is enabled: {code:title=OpenShiftDebugUtils#getDebuggingContext} debugContext.setDebugEnabled(Boolean.parseBoolean(debugEnabled) || Boolean.parseBoolean(devModeEnabled)); {code} Thus when the server adapter starts the debugger he erroneously thinks that debugging is already active and wont reenable it. The following change *FIXES* it, the debugger is started correctly, no port error happens. {code} debugContext.setDebugEnabled(Boolean.parseBoolean(debugEnabled)); {code} But I'm very unsure about the side-effects. Maybe this now is only true for nodejs and will affect eap, too. We have to test this change throughoutly before applying it. [~fbricon] do you remember why debugging is considered enabled when dev_mode is enabled? > Server adapter: "Start/Restart in Debug" is broken for Nodejs > ------------------------------------------------------------- > > Key: JBIDE-23961 > URL: https://issues.jboss.org/browse/JBIDE-23961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Priority: Critical > Attachments: image-2017-02-16-23-30-21-709.png, server-adapter-erroneous-debugging-state.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23961 at 2/16/17 6:52 PM: ------------------------------------------------------------------- The cause for this is the following: In JBIDE-22362 we always enabled DEV_MODE. When launching the debugger one finds the following code that checks if the debugging is enabled: {code:title=OpenShiftDebugUtils#getDebuggingContext} debugContext.setDebugEnabled(Boolean.parseBoolean(debugEnabled) || Boolean.parseBoolean(devModeEnabled)); {code} Thus when the server adapter starts the debugger he erroneously thinks that debugging is already active and wont reenable it. The following change *FIXES* it, the debugger is started correctly, no port error happens. {code} debugContext.setDebugEnabled(Boolean.parseBoolean(debugEnabled)); {code} But I'm very unsure about the side-effects. Maybe this now is only true for nodejs and will affect eap, too. We have to test this change throughoutly before applying it. [~fbricon] do you remember why debugging is considered enabled when dev_mode is enabled? was (Author: adietish): The cause for this is the following: In JBIDE-22362 we always enabled DEV_MODE. When launching the debugger one finds the following code that checks if the debugging is enabled: {code:title=OpenShiftDebugUtils#getDebuggingContext} debugContext.setDebugEnabled(Boolean.parseBoolean(debugEnabled) || Boolean.parseBoolean(devModeEnabled)); {code} Thus when the server adapter starts the debugger he erroneously thinks that debugging is already active and wont reenable it. The following change *FIXES* it, the debugger is started correctly, no port error happens. {code} debugContext.setDebugEnabled(Boolean.parseBoolean(debugEnabled)); {code} But I'm very unsure about the side-effects. Maybe this now is only true for nodejs and will affect eap, too. We have to test this change throughoutly before applying it. > Server adapter: "Start/Restart in Debug" is broken for Nodejs > ------------------------------------------------------------- > > Key: JBIDE-23961 > URL: https://issues.jboss.org/browse/JBIDE-23961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Priority: Critical > Attachments: image-2017-02-16-23-30-21-709.png, server-adapter-erroneous-debugging-state.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23961 at 2/16/17 6:50 PM: ------------------------------------------------------------------- The cause for this is the following: In JBIDE-22362 we always enabled DEV_MODE. When launching the debugger one finds the following code that checks if the debugging is enabled: {code:title=OpenShiftDebugUtils#getDebuggingContext} debugContext.setDebugEnabled(Boolean.parseBoolean(debugEnabled) || Boolean.parseBoolean(devModeEnabled)); {code} Thus when the server adapter starts the debugger he erroneously thinks that debugging is already active and wont reenable it. The following change *FIXES* it, the debugger is started correctly, no port error happens. {code} debugContext.setDebugEnabled(Boolean.parseBoolean(debugEnabled)); {code} But I'm very unsure about the side-effects. Maybe this now is only true for nodejs and will affect eap, too. We have to test this change throughoutly before applying it. was (Author: adietish): The cause for this is the following: In JBIDE-22362 we always enabled DEV_MODE. When launching the debugger one finds the following code that checks if the debugging is enabled: {code:title=OpenShiftDebugUtils#getDebuggingContext} debugContext.setDebugEnabled(Boolean.parseBoolean(debugEnabled) || Boolean.parseBoolean(devModeEnabled)); {code} Thus when the server adapter starts the debugger he erroneously thinks that debugging is already active and wont reenable it. The following change *FIXES* it, the debugger is started correctly, no port error happens. {code} debugContext.setDebugEnabled(Boolean.parseBoolean(debugEnabled)); {code} But I'm very unsure about the side-effects. Maybe this now is only true for nodejs and will affect eap, too. > Server adapter: "Start/Restart in Debug" is broken for Nodejs > ------------------------------------------------------------- > > Key: JBIDE-23961 > URL: https://issues.jboss.org/browse/JBIDE-23961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Priority: Critical > Attachments: image-2017-02-16-23-30-21-709.png, server-adapter-erroneous-debugging-state.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23961 at 2/16/17 6:50 PM: ------------------------------------------------------------------- The cause for this is the following: In JBIDE-22362 we always enabled DEV_MODE. When launching the debugger one finds the following code that checks if the debugging is enabled: {code:title=OpenShiftDebugUtils#getDebuggingContext} debugContext.setDebugEnabled(Boolean.parseBoolean(debugEnabled) || Boolean.parseBoolean(devModeEnabled)); {code} Thus when the server adapter starts the debugger he erroneously thinks that debugging is already active and wont reenable it. The following change *FIXES* it, the debugger is started correctly, no port error happens. {code} debugContext.setDebugEnabled(Boolean.parseBoolean(debugEnabled)); {code} But I'm very unsure about the side-effects. Maybe this now is only true for nodejs and will affect eap, too. was (Author: adietish): The cause for this is the following: In JBIDE-22362 we always enabled DEV_MODE. When launching the debugger one finds the following code that checks if the debugging is enabled: {code:title=OpenShiftDebugUtils#getDebuggingContext} debugContext.setDebugEnabled(Boolean.parseBoolean(debugEnabled) || Boolean.parseBoolean(devModeEnabled)); {code} Thus when the server adapter starts the debugger he erroneously thinks that debugging is already active and wont reenable it. changing it to {code} debugContext.setDebugEnabled(Boolean.parseBoolean(debugEnabled)); {code} But I'm very unsure about the side-effects. Maybe this now is only true for nodejs and will affect eap, too. > Server adapter: "Start/Restart in Debug" is broken for Nodejs > ------------------------------------------------------------- > > Key: JBIDE-23961 > URL: https://issues.jboss.org/browse/JBIDE-23961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Priority: Critical > Attachments: image-2017-02-16-23-30-21-709.png, server-adapter-erroneous-debugging-state.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2017