[jbosstools-issues] [JBoss JIRA] (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

[Andre Dietisheim (JIRA)]

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

Andre Dietisheim commented on JBIDE-24868:
------------------------------------------

[~aurelien.pupier] [~jeffmaury] [~dbocharov] the PR was updated to now set a route timeout and "disable" liveness probe (by increasing the initial delay). Both values are restored once you get back to run (from debugging). Dare to test it please? https://github.com/jbosstools/jbosstools-openshift/pull/1582

> Server adapter: Node.js debug session terminated after 30s, browser shows 502 gateway error: set route timeout and disable pod livenessProbe.periodSecond property
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-24868
>                 URL: https://issues.jboss.org/browse/JBIDE-24868
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.5.0.Final
>            Reporter: Aurélien Pupier
>            Assignee: Andre Dietisheim
>              Labels: openshift_v3, server_adapter
>             Fix For: 4.5.2.AM1
>
>         Attachments: application-is-not-available.png, breakpoint-suspend-thread.png, webui_edit-add-service.png
>
>
> it will avoid to have "debug connections always killed after 30s staying in a breakpoint"
> see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion
> k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)