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

[UPSTREAM] Server adapter: debugging fails for nodejs-mongo-persistent template based application

    XMLWordPrintable

Details

    Description

      steps:

      1. ASSERT: have cdk 3.6.0
      2. 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
      3. EXEC: start the server adapter
      4. ASSERT: server adapter is [Started, Synchronized]
      5. 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.

      The debugger is therefore stopped, debugging wont work.

      Trying to restart it reproduces the error that we already have.
      In the Eclipse log you'll find the following:

      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

      Attachments

        1. screenshot-1.png
          screenshot-1.png
          31 kB
        2. screenshot-2.png
          screenshot-2.png
          35 kB
        3. change-nodejs-version.png
          change-nodejs-version.png
          148 kB

        Issue Links

          is related to

          Feature Request - Feature requests from customers and/or users JBIDE-26870 Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-26158 [UPSTREAM] Server adapter: NPE when starting adapter for nodejs-mongo-persistent into Debug

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-26160 Server Adapter: erroneously stays in [Debugging] when you kill the pod

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-25000 Server adapter: starting into debugging fails initially (succeeds on a latter try)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Activity

            People

              jmaury@redhat.com Jeff MAURY
              adietish@redhat.com André Dietisheim
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: