[JBoss JIRA] (JBIDE-24965) Server adapter: fails to "Restart in Debug"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24965?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24965:
-------------------------------------
Sprint: devex #138 September 2017 (was: devex #137 September 2017)
> Server adapter: fails to "Restart in Debug"
> -------------------------------------------
>
> Key: JBIDE-24965
> URL: https://issues.jboss.org/browse/JBIDE-24965
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.1.AM2
>
> Attachments: image-2017-09-02-01-06-58-751.png
>
>
> steps:
> # EXEC: Create a nodejs-mongo-persistent application
> # EXEC/ASSERT: Create a server adapter for the service nodejs-mongo-persistent
> # EXEC: start the server adapter via "Debug"
> # ASSERT: debugging works
> # EXEC: restart the server adapter via "Restart in Debug"
> Result:
> Debugging fails, you get the following error:
> !image-2017-09-02-01-06-58-751.png!
> In the log you find the following entry:
> {code}
> org.eclipse.core.runtime.CoreException: Could not find running pod to forward to in server adapter "nodejs-mongo-persistent (Service) at OpenShift 3 (192.168.64.2)"
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.mapPortForwarding(OpenShiftLaunchController.java:357)
> 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:83)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:221)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.launch(OpenShiftNodejsLaunchController.java:52)
> 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:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> 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:56)
> !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-09-02 00:32:34.031
> !MESSAGE Could not find running pod to forward to in server adapter "nodejs-mongo-persistent (Service) at OpenShift 3 (192.168.64.2)"
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25000:
-------------------------------------
Sprint: devex #138 September 2017 (was: devex #137 September 2017)
> Server adapter: starting into debugging fails initially (succeeds on a latter try)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-25000
> URL: https://issues.jboss.org/browse/JBIDE-25000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.5.1.AM3
>
> Attachments: failed-to-connect-v8-vm.png
>
>
> # ASSERT: have an application running in OpenShift based on the "nodejs-mongo-persistent" template
> # ASSERT: have a server adapter for it
> # EXEC/ASSERT: have the adapter started in non-debugging/normal mode
> # EXEC: restart the adapter debugging
> Result:
> !failed-to-connect-v8-vm.png!
> {code}
> java.io.IOException: Failed to get version
> 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:132)
> 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:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
> ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months