-
Bug
-
Resolution: Duplicate
-
Critical
-
4.4.2.AM2
-
devex #130 April 2017
-
10
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)
- is duplicated by
-
JBIDE-24868 Server adapter: Node.js debug session terminated after 30s, browser shows 502 gateway error: set route timeout and disable pod livenessProbe.periodSecond property
- Closed
- is related to
-
JBIDE-23470 Server Adapter: stuck restarting in debug mode
- Closed
- relates to
-
JBIDE-22225 Debugging for node.js applications on Openshift
- Closed
-
JBIDE-23961 Server adapter: "Start/Restart in Debug" is broken for Nodejs
- Closed