]
Jeff Cantrill commented on JBIDE-23422:
---------------------------------------
Thinking about this further, I don't understand how the router is involved in this
workflow. From what I recall, we use 'oc debug' to connect to the pod which would
not route any traffic through the router. There are additional switched that may be of
use. Do we have this same issue using oc to connect to the pod directly outside of
eclipse?
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)