[jbosstools-issues] [JBoss JIRA] (JBIDE-26408) [UPSTREAM] Server adapter: debugging fails for nodejs-mongo-persistent template based application

[André Dietisheim (Jira)]

     [ https://issues.jboss.org/browse/JBIDE-26408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

André Dietisheim updated JBIDE-26408:
-------------------------------------
    Comment: was deleted

(was: [~jeffmaury] can you please add 4.13.x fixVersion? This needs to be kept open to track upstream developement in Eclipse (or the lack thereof).)


> [UPSTREAM] Server adapter: debugging fails for nodejs-mongo-persistent template based application
> -------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-26408
>                 URL: https://issues.jboss.org/browse/JBIDE-26408
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.9.0.Final
>         Environment: cdk-3.6.0+
>            Reporter: André Dietisheim
>            Assignee: Jeff MAURY
>            Priority: Major
>              Labels: node, server_adapter, upstream
>             Fix For: 4.14.x
>
>         Attachments: change-nodejs-version.png, screenshot-1.png, screenshot-2.png
>
>
> 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, debugging wont work.
>  !screenshot-2.png! 
> 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.13.8#713008)