Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-25000

Server adapter: starting into debugging fails initially (succeeds on a latter try)

    Details

    • Sprint:
      devex #138 September 2017, devex #152 July 2018, devex #153 August 2018, devex #154 September 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019, devex #158 November 2018
    • Story Points:
      13
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      restart the adapter in debug, it works either immediately or eventually in latter tries

      Show
      restart the adapter in debug, it works either immediately or eventually in latter tries

      Description

      1. ASSERT: have an application running in OpenShift Online based on the "nodejs-mongo-persistent" template
      2. ASSERT: have a server adapter for it
      3. EXEC/ASSERT: have the adapter started in non-debugging/normal mode
      4. EXEC: restart the adapter debugging

      Result:

      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)
      

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  adietish André Dietisheim
                  Reporter:
                  adietish André Dietisheim
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated: