[jbosstools-issues] [JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error

[Ilya Buziuk (JIRA)]

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

Ilya Buziuk commented on JBIDE-23422:
-------------------------------------

[~adietish], debugging code from openshift.js bundle does not handle connection creation - it just passes required parameters like host / port to chromium launch configuration [1]. Connection part is a low level thing that is done in wst.jsdt.chromium bundle [2]

[1] https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/org.jboss.tools.openshift.js/src/org/jboss/tools/openshift/js/launcher/NodeDebugLauncher.java
[2] http://git.eclipse.org/c/jsdt/webtools.jsdt.git/tree/bundles/org.eclipse.wst.jsdt.chromium/src/org/eclipse/wst/jsdt/chromium/internal/transport/SocketConnection.java

> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-23422
>                 URL: https://issues.jboss.org/browse/JBIDE-23422
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: javascript, openshift
>    Affects Versions: 4.4.2.AM2
>         Environment: windows 10
> Fedora 24
>            Reporter: Ilya Buziuk
>            Assignee: Jeff MAURY
>            Priority: Critical
>              Labels: nodejs, openshift_v3, server_adapter
>             Fix For: 4.4.3.Final
>
>
>  We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)



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