[jbosstools-issues] [JBoss JIRA] (JBIDE-24083) Debug NodeJS app is broken - Failed to connect to Standalone V8 VM

Andre Dietisheim (JIRA) issues at jboss.org
Wed Mar 29 08:53:00 EDT 2017


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

Andre Dietisheim commented on JBIDE-24083:
------------------------------------------

my bad, node debugging is enabled via the *DEV_MODE* env var and *NOT* the *DEBUG* env var!
If you manually add the DEV_MODE env var to the replication controller, wait until the new pod is deployed and then restart your adapter in debug mode everything is fine.
So we're missing the DEV_MODE.
[~jeffmaury] dont we run node apps in DEV_MODE by default? Need to investigate why we're missing DEV_MODE for node

> Debug NodeJS app is broken - Failed to connect to Standalone V8 VM
> ------------------------------------------------------------------
>
>                 Key: JBIDE-24083
>                 URL: https://issues.jboss.org/browse/JBIDE-24083
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift, server
>    Affects Versions: 4.4.4.AM1
>            Reporter: Pavol Srna
>            Assignee: Andre Dietisheim
>            Priority: Critical
>              Labels: regression
>             Fix For: 4.4.4.AM2
>
>         Attachments: jbide-23961-restart-1.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:55)
> 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}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jbosstools-issues mailing list