[jbosstools-issues] [JBoss JIRA] (JBIDE-26408) Server adapter: start into debugging fails for nodejs template application

[ https://issues.jboss.org/browse/JBIDE-26408?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26408: ------------------------------------- Description: steps: # ASSERT: have cdk 3.6.0 # 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 # EXEC: start the server adapter # ASSERT: server adapter is *[Started, Synchronized]* # 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. !screenshot-1.png! The debugger is therefore stopped. Trying to restart it reproduces the error that we already have. !screenshot-2.png! In the Eclipse log you'll find the following: {code} 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 {code} was: steps: # ASSERT: have cdk 3.6.0 # 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 # EXEC: start the server adapter # ASSERT: server adapter is *[Started, Synchronized]* # 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. Trying to restart it reproduces the error that we already have. In the Eclipse log you'll find the following: {code} 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 {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)