[jbosstools-issues] [JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)

Andre Dietisheim (JIRA) issues at jboss.org
Fri Sep 8 17:23:00 EDT 2017


    [ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461215#comment-13461215 ] 

Andre Dietisheim commented on JBIDE-25000:
------------------------------------------

This very much looks like we're trying to connect to nodejs when it's not fully up yet bcs the issue wont happen in the 2nd restart (mostly). The same is suggested since the issue wont happen you start the adapter in debug when the app is in debug mode already (check env vars in the service/dc, verify that it has devmode set to "true" and the debug port to some numerical value).
We're waiting for the pod to run, but not for nodejs to be up.

> 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.AM2
>
>         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|thumbnail! 
> {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}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jbosstools-issues mailing list