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

Rob Cernich (JIRA) issues at jboss.org
Fri Feb 3 11:48:00 EST 2017


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

Rob Cernich commented on JBIDE-23422:
-------------------------------------

There is a timeout on the port-forwarder itself:

https://github.com/openshift/origin/blob/master/vendor/k8s.io/kubernetes/pkg/kubelet/server/portforward/portforward.go#L155-L158

https://github.com/openshift/origin/blob/master/vendor/k8s.io/kubernetes/pkg/kubelet/server/server.go#L726

https://github.com/openshift/origin/blob/master/vendor/k8s.io/kubernetes/pkg/kubelet/kubelet.go#L2094

Can't find where the default is set, but here's a start (it's a config option): https://github.com/openshift/origin/blob/master/vendor/k8s.io/kubernetes/cmd/kubelet/app/options/options.go#L168

> 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: Andre Dietisheim
>            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)


More information about the jbosstools-issues mailing list