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

[Andre Dietisheim (JIRA)]

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

Andre Dietisheim edited comment on JBIDE-25000 at 7/3/18 8:55 AM:
------------------------------------------------------------------

I tried 2 approaches, but both didn't work:
* catch the connection error and try again:
  doesn't work, the error occurrs in a different thread
* connect beforehand via a dummy socket to see if the port is ready:
  doesn't work, port forwarding lets you always connect but this wont tell you if the end of the pipe is ready.

It looks to me as if the only way to achieve this is to make sure that there's a readyness probe for the debug-port, too?
[~jeffmaury] Thoughts?


was (Author: adietish):
I tried 2 approaches, but both didn't work:
* catch the connection error and try again:
  doesn't work, the error occurrs in a different thread
* connect beforehand via a dummy socket to see if the port is ready:
  doesn't work, port forwarding lets you always connect but this wont tell you if the end of the pipe is ready.
It looks to me as if the only way to achieve this is to make sure that there's a readyness probe for the debug-port, too?
[~jeffmaury] Thoughts?

> 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
>              Labels: openshift_v3, server_adapter
>             Fix For: 4.6.0.Final
>
>         Attachments: failed-to-connect-v8-vm.png
>
>
> # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* 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.5.0#75005)