[jbosstools-issues] [JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session (Node.js debug session terminated after 30s, browser shows 502 gateway error)

Andre Dietisheim (JIRA) issues at jboss.org
Sat Oct 28 10:06:00 EDT 2017


     [ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim updated JBIDE-24868:
-------------------------------------
    Summary: Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session (Node.js debug session terminated after 30s, browser shows 502 gateway error)  (was: Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session)


> Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session (Node.js debug session terminated after 30s, browser shows 502 gateway error)
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-24868
>                 URL: https://issues.jboss.org/browse/JBIDE-24868
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          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)



More information about the jbosstools-issues mailing list