[JBoss JIRA] (JBIDE-26408) Server adapter: debugging fails for nodejs-mongo-persistent template based application
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26408?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26408:
------------------------------------------
JBIDE-25000 is not a duplicate. That bug occurs because the Eclipse debugger tries to connect before the node debugger is ready in OpenShift. That is a "readyness" (probe) bug.
> Server adapter: debugging fails for nodejs-mongo-persistent template based application
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-26408
> URL: https://issues.jboss.org/browse/JBIDE-26408
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.Final
> Environment: cdk-3.6.0
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Priority: Major
> Labels: node, server_adapter
> Fix For: 4.10.0.AM1
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> steps:
> # ASSERT: have cdk 3.6.0
> # EXEC: create an application based on the *nodejs-mongo-persistent* template, have the application imported to the workspace and the server adapter created for it
> # EXEC: start the server adapter
> # ASSERT: server adapter is *[Started, Synchronized]*
> # EXEC: Restart the adapter into debugging
> Result:
> You very quickly (the timeout seems very short) get an error dialog telling you that the debugger could not connect.
> !screenshot-1.png!
> The debugger is therefore stopped, debugging wont work.
> !screenshot-2.png!
> Trying to restart it reproduces the error that we already have.
> In the Eclipse log you'll find the following:
> {code}
> java.io.IOException: Timed out waiting for handshake
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:134)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:859)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1026)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$2.run(DebugUIPlugin.java:1240)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> Caused by: java.util.concurrent.TimeoutException
> at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:204)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26408) Server adapter: debugging fails for nodejs-mongo-persistent template based application
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26408?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26408:
------------------------------------------
Once the debugging works (if we get the support is wsdt) one hits the following bug: JBIDE-26158
> Server adapter: debugging fails for nodejs-mongo-persistent template based application
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-26408
> URL: https://issues.jboss.org/browse/JBIDE-26408
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.Final
> Environment: cdk-3.6.0
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Priority: Major
> Labels: node, server_adapter
> Fix For: 4.10.0.AM1
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> steps:
> # ASSERT: have cdk 3.6.0
> # EXEC: create an application based on the *nodejs-mongo-persistent* template, have the application imported to the workspace and the server adapter created for it
> # EXEC: start the server adapter
> # ASSERT: server adapter is *[Started, Synchronized]*
> # EXEC: Restart the adapter into debugging
> Result:
> You very quickly (the timeout seems very short) get an error dialog telling you that the debugger could not connect.
> !screenshot-1.png!
> The debugger is therefore stopped, debugging wont work.
> !screenshot-2.png!
> Trying to restart it reproduces the error that we already have.
> In the Eclipse log you'll find the following:
> {code}
> java.io.IOException: Timed out waiting for handshake
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:134)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:859)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1026)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$2.run(DebugUIPlugin.java:1240)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> Caused by: java.util.concurrent.TimeoutException
> at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:204)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26408) Server adapter: debugging fails for nodejs-mongo-persistent template based application
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26408?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26408:
------------------------------------------
A request to upgrade chrome devtools in wsdt to support the inspect protocol (that replaced the deprecated debug protocol around node 8) is Eclipse bugzilla at: https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907
> Server adapter: debugging fails for nodejs-mongo-persistent template based application
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-26408
> URL: https://issues.jboss.org/browse/JBIDE-26408
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.Final
> Environment: cdk-3.6.0
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Priority: Major
> Labels: node, server_adapter
> Fix For: 4.10.0.AM1
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> steps:
> # ASSERT: have cdk 3.6.0
> # EXEC: create an application based on the *nodejs-mongo-persistent* template, have the application imported to the workspace and the server adapter created for it
> # EXEC: start the server adapter
> # ASSERT: server adapter is *[Started, Synchronized]*
> # EXEC: Restart the adapter into debugging
> Result:
> You very quickly (the timeout seems very short) get an error dialog telling you that the debugger could not connect.
> !screenshot-1.png!
> The debugger is therefore stopped, debugging wont work.
> !screenshot-2.png!
> Trying to restart it reproduces the error that we already have.
> In the Eclipse log you'll find the following:
> {code}
> java.io.IOException: Timed out waiting for handshake
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:134)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:859)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1026)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$2.run(DebugUIPlugin.java:1240)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> Caused by: java.util.concurrent.TimeoutException
> at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:204)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26158) [UPSTREAM] Server adapter: NPE when starting adapter into Debug
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26158?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26158:
------------------------------------------
Pushing this upstream watching bug to 4.10.X
> [UPSTREAM] Server adapter: NPE when starting adapter into Debug
> ----------------------------------------------------------------
>
> Key: JBIDE-26158
> URL: https://issues.jboss.org/browse/JBIDE-26158
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Major
> Labels: upstream
> Fix For: 4.10.x
>
> Attachments: image-2018-07-02-22-33-13-396.png, image-2018-07-02-22-49-45-246.png, image-2018-07-02-23-17-34-099.png, image-2018-07-03-00-03-56-346.png, screenshot-1.png, screenshot-2.png
>
>
> steps:
> # EXEC: launch new application wizard, choose nodejs-mongo-persistent template and finish
> # EXEC: when asked import the app and create a server adapter
> # ASSERT: server adapter is created
> # EXEC: start the server adapter
> # ASSERT: server adapter is launched
> # EXEC: restart the server adapter into Debug
> Result:
> Debuggin works, but you get the following error dialog:
> !image-2018-07-02-22-33-13-396.png!
> In the Eclipse log you'll find the following:
> {code}
> java.lang.NullPointerException
> at org.eclipse.core.internal.resources.CheckMissingNaturesListener.updateRange(CheckMissingNaturesListener.java:209)
> at org.eclipse.core.internal.resources.CheckMissingNaturesListener$3.runInWorkspace(CheckMissingNaturesListener.java:179)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
> ps. project context menu: Convert > Javascript Project doesn't help.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26158) [UPSTREAM] Server adapter: NPE when starting adapter into Debug
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26158?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26158:
-------------------------------------
Fix Version/s: 4.10.x
(was: 4.10.0.AM1)
> [UPSTREAM] Server adapter: NPE when starting adapter into Debug
> ----------------------------------------------------------------
>
> Key: JBIDE-26158
> URL: https://issues.jboss.org/browse/JBIDE-26158
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Major
> Labels: upstream
> Fix For: 4.10.x
>
> Attachments: image-2018-07-02-22-33-13-396.png, image-2018-07-02-22-49-45-246.png, image-2018-07-02-23-17-34-099.png, image-2018-07-03-00-03-56-346.png, screenshot-1.png, screenshot-2.png
>
>
> steps:
> # EXEC: launch new application wizard, choose nodejs-mongo-persistent template and finish
> # EXEC: when asked import the app and create a server adapter
> # ASSERT: server adapter is created
> # EXEC: start the server adapter
> # ASSERT: server adapter is launched
> # EXEC: restart the server adapter into Debug
> Result:
> Debuggin works, but you get the following error dialog:
> !image-2018-07-02-22-33-13-396.png!
> In the Eclipse log you'll find the following:
> {code}
> java.lang.NullPointerException
> at org.eclipse.core.internal.resources.CheckMissingNaturesListener.updateRange(CheckMissingNaturesListener.java:209)
> at org.eclipse.core.internal.resources.CheckMissingNaturesListener$3.runInWorkspace(CheckMissingNaturesListener.java:179)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
> ps. project context menu: Convert > Javascript Project doesn't help.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26158) Server adapter: NPE when starting adapter into Debug
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26158?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26158:
------------------------------------------
[~mickael_istria] I filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=540260 in Eclipse platform/Resources.
> Server adapter: NPE when starting adapter into Debug
> -----------------------------------------------------
>
> Key: JBIDE-26158
> URL: https://issues.jboss.org/browse/JBIDE-26158
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Major
> Labels: upstream
> Fix For: 4.10.0.AM1
>
> Attachments: image-2018-07-02-22-33-13-396.png, image-2018-07-02-22-49-45-246.png, image-2018-07-02-23-17-34-099.png, image-2018-07-03-00-03-56-346.png, screenshot-1.png, screenshot-2.png
>
>
> steps:
> # EXEC: launch new application wizard, choose nodejs-mongo-persistent template and finish
> # EXEC: when asked import the app and create a server adapter
> # ASSERT: server adapter is created
> # EXEC: start the server adapter
> # ASSERT: server adapter is launched
> # EXEC: restart the server adapter into Debug
> Result:
> Debuggin works, but you get the following error dialog:
> !image-2018-07-02-22-33-13-396.png!
> In the Eclipse log you'll find the following:
> {code}
> java.lang.NullPointerException
> at org.eclipse.core.internal.resources.CheckMissingNaturesListener.updateRange(CheckMissingNaturesListener.java:209)
> at org.eclipse.core.internal.resources.CheckMissingNaturesListener$3.runInWorkspace(CheckMissingNaturesListener.java:179)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
> ps. project context menu: Convert > Javascript Project doesn't help.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26158) [UPSTREAM] Server adapter: NPE when starting adapter into Debug
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26158?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26158:
-------------------------------------
Summary: [UPSTREAM] Server adapter: NPE when starting adapter into Debug (was: Server adapter: NPE when starting adapter into Debug )
> [UPSTREAM] Server adapter: NPE when starting adapter into Debug
> ----------------------------------------------------------------
>
> Key: JBIDE-26158
> URL: https://issues.jboss.org/browse/JBIDE-26158
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Major
> Labels: upstream
> Fix For: 4.10.0.AM1
>
> Attachments: image-2018-07-02-22-33-13-396.png, image-2018-07-02-22-49-45-246.png, image-2018-07-02-23-17-34-099.png, image-2018-07-03-00-03-56-346.png, screenshot-1.png, screenshot-2.png
>
>
> steps:
> # EXEC: launch new application wizard, choose nodejs-mongo-persistent template and finish
> # EXEC: when asked import the app and create a server adapter
> # ASSERT: server adapter is created
> # EXEC: start the server adapter
> # ASSERT: server adapter is launched
> # EXEC: restart the server adapter into Debug
> Result:
> Debuggin works, but you get the following error dialog:
> !image-2018-07-02-22-33-13-396.png!
> In the Eclipse log you'll find the following:
> {code}
> java.lang.NullPointerException
> at org.eclipse.core.internal.resources.CheckMissingNaturesListener.updateRange(CheckMissingNaturesListener.java:209)
> at org.eclipse.core.internal.resources.CheckMissingNaturesListener$3.runInWorkspace(CheckMissingNaturesListener.java:179)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
> ps. project context menu: Convert > Javascript Project doesn't help.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26158) [UPSTREAM] Server adapter: NPE when starting adapter into Debug
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26158?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26158:
-------------------------------------
Forum Reference: https://bugs.eclipse.org/bugs/show_bug.cgi?id=540260
> [UPSTREAM] Server adapter: NPE when starting adapter into Debug
> ----------------------------------------------------------------
>
> Key: JBIDE-26158
> URL: https://issues.jboss.org/browse/JBIDE-26158
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Major
> Labels: upstream
> Fix For: 4.10.0.AM1
>
> Attachments: image-2018-07-02-22-33-13-396.png, image-2018-07-02-22-49-45-246.png, image-2018-07-02-23-17-34-099.png, image-2018-07-03-00-03-56-346.png, screenshot-1.png, screenshot-2.png
>
>
> steps:
> # EXEC: launch new application wizard, choose nodejs-mongo-persistent template and finish
> # EXEC: when asked import the app and create a server adapter
> # ASSERT: server adapter is created
> # EXEC: start the server adapter
> # ASSERT: server adapter is launched
> # EXEC: restart the server adapter into Debug
> Result:
> Debuggin works, but you get the following error dialog:
> !image-2018-07-02-22-33-13-396.png!
> In the Eclipse log you'll find the following:
> {code}
> java.lang.NullPointerException
> at org.eclipse.core.internal.resources.CheckMissingNaturesListener.updateRange(CheckMissingNaturesListener.java:209)
> at org.eclipse.core.internal.resources.CheckMissingNaturesListener$3.runInWorkspace(CheckMissingNaturesListener.java:179)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
> ps. project context menu: Convert > Javascript Project doesn't help.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26407) Server adapter: fails with a NPE if there's no oc configured
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26407?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26407:
------------------------------------------
[~dbocharov] ok cool, that explains it :)
> Server adapter: fails with a NPE if there's no oc configured
> -------------------------------------------------------------
>
> Key: JBIDE-26407
> URL: https://issues.jboss.org/browse/JBIDE-26407
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Major
> Labels: oc_binary, server_adapter
> Fix For: 4.10.0.AM1
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> steps:
> # ASSERT: start with a workspace where's no preference that points to an oc binary
> # ASSERT: have the connection *NOT* overriding the oc binary location
> # EXEC: create a new application (ex. by using the *nodejs-mongo-persistent* template), have the project imported to your workspace and the server adapter created
> # EXEC: start the server adapter
> Result:
> you get an error dialog reporting an NPE
> !screenshot-1.png!
> The following can be spotted in the Eclipse log:
> {code}
> java.lang.NullPointerException
> at java.base/java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1022)
> at java.base/java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1017)
> at com.openshift.restclient.OpenShiftContext.put(OpenShiftContext.java:51)
> at org.jboss.tools.openshift.internal.core.ocbinary.OCBinaryOperation.run(OCBinaryOperation.java:27)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:156)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:148)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startPortForwarding(OpenShiftLaunchController.java:402)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.access$0(OpenShiftNodejsLaunchController.java:1)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController$1.onDebugChange(OpenShiftNodejsLaunchController.java:36)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:252)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:186)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.updateOpenShift(OpenShiftLaunchController.java:147)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:96)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:859)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:712)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months