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

Andre Dietisheim (JIRA) issues at jboss.org
Wed Nov 16 13:04:00 EST 2016


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

Andre Dietisheim edited comment on JBIDE-23422 at 11/16/16 1:03 PM:
--------------------------------------------------------------------

[~jcantrill] thx, I was pointed to the same PR and if I read it carefully I see the following options that we can set to the env vars of the deployment config:
{quote}
`*ROUTER_DEFAULT_CLIENT_TIMEOUT*`| 30s | How long a client has to acknowledge or send data.
`*ROUTER_DEFAULT_CONNECT_TIMEOUT*`| 5s | The maximum connect time.
`*ROUTER_DEFAULT_SERVER_TIMEOUT*`| 30s | How long a server has to acknowledge or send data.
`*ROUTER_DEFAULT_TUNNEL_TIMEOUT*` | 1h | How long to allow TCP or WebSocket connections to remain open.
{quote}
So when enabling debugging we should be able to alter the deployment config of the router?


was (Author: adietish):
[~jcantrill] thx, I was pointed to the same PR and if I read it carefully I see the following options that we can set to the env vars of the deployment config:
{quote}
`*ROUTER_DEFAULT_CLIENT_TIMEOUT*`| 30s | How long a client has to acknowledge or send data.
`*ROUTER_DEFAULT_CONNECT_TIMEOUT*`| 5s | The maximum connect time.
`*ROUTER_DEFAULT_SERVER_TIMEOUT*`| 30s | How long a server has to acknowledge or send data.
`*ROUTER_DEFAULT_TUNNEL_TIMEOUT*` | 1h | How long to allow TCP or WebSocket connections to remain open.
{quote}

> 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: Ilya Buziuk
>            Priority: Critical
>              Labels: nodejs, openshift_v3, server_adapter
>             Fix For: 4.4.2.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)


More information about the jbosstools-issues mailing list