[jbosstools-issues] [JBoss JIRA] (JBIDE-23422) Node.js debug session is terminated after ~1 minute and browser shows 502 error
Ilya Buziuk (JIRA)
issues at jboss.org
Thu Oct 27 12:15:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13313129#comment-13313129 ]
Ilya Buziuk commented on JBIDE-23422:
-------------------------------------
Can not reproduce on Ubuntu 16.04 - https://youtu.be/GmQzp_jU754
As you can see debug session is running for more than 4 minutes without 502 error. There is 504 tirameout error which does not terminate debug session but this is expected IMO
cc [~rhopp], [~jrichter1], [~mlabuda]
> 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
> 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.2#72004)
More information about the jbosstools-issues
mailing list