[jbosstools-issues] [JBoss JIRA] (ERT-221) Exception when debugging with chromium [EBZ#494731]

[Gorkem Ercan (JIRA)]

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

Gorkem Ercan updated ERT-221:
-----------------------------
    Story Points: 2


> Exception when debugging with chromium [EBZ#494731]
> ---------------------------------------------------
>
>                 Key: ERT-221
>                 URL: https://issues.jboss.org/browse/ERT-221
>             Project: Eclipse Release Train
>          Issue Type: Task
>          Components: JSDT
>            Reporter: Friendly Jira Robot
>              Labels: 3.8_RC3, Debug, bzira
>             Fix For: Neon (4.6) RC3
>
>
> Using EPP JavaScript RC2 package, using "Debug As > Node.js application" on some random file.
> This error seems to happen whenever the program is interrupted, for example because a dependency doesn't compile or whatever.
> Such remote interruption can happen pretty often, the shouldn't be treated as IDE error, but rather caught and presented to the user. Currently, it's logged in the IDE, and AERI suggests to open a ticket for that despite there is nothing wrong in the IDE. This gives an impression that debugger has bugs and this is going to flood AERI with no fair reason.
> --
> eclipse.buildId=4.6.0.I20160519-1730
> java.version=1.8.0_77
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments:  -product org.eclipse.epp.package.javascript.product
> Command-line arguments:  -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.javascript.product
> org.eclipse.wst.jsdt.chromium.debug.core
> Error
> Fri May 27 11:23:55 CEST 2016
> SDK:org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection: Exception in message listener
> java.lang.IllegalStateException: Connection not attached
> 	at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection.checkAttached(SocketConnection.java:455)
> 	at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection.send(SocketConnection.java:416)
> 	at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl$V8CommandOutputImpl.send(StandaloneVmImpl.java:249)
> 	at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.send(V8CommandProcessor.java:133)
> 	at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.send(V8CommandProcessor.java:1)
> 	at org.eclipse.wst.jsdt.chromium.internal.BaseCommandProcessor.send(BaseCommandProcessor.java:75)
> 	at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor.sendV8CommandAsync(V8CommandProcessor.java:84)
> 	at org.eclipse.wst.jsdt.chromium.internal.v8native.DebugSession.sendMessageAsync(DebugSession.java:101)
> 	at org.eclipse.wst.jsdt.chromium.internal.v8native.processor.AfterCompileProcessor.messageReceived(AfterCompileProcessor.java:44)
> 	at org.eclipse.wst.jsdt.chromium.internal.v8native.DefaultResponseHandler.handleResponseWithHandler(DefaultResponseHandler.java:60)
> 	at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.acceptNonSeq(V8CommandProcessor.java:145)
> 	at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.acceptNonSeq(V8CommandProcessor.java:1)
> 	at org.eclipse.wst.jsdt.chromium.internal.BaseCommandProcessor.processIncoming(BaseCommandProcessor.java:112)
> 	at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor.processIncomingJson(V8CommandProcessor.java:115)
> 	at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl$4.messageReceived(StandaloneVmImpl.java:116)
> 	at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$RegularMessageItem.report(SocketConnection.java:122)
> 	at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ResponseDispatcherThread.run(SocketConnection.java:211)



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)