[jbosstools-issues] [JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

[Roland Huß (JIRA)]

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

Roland Huß commented on JBIDE-24868:
------------------------------------

The OpenShift annotation for the route sounds promising and it would be the easiest way to solve this problem (if it works, never tried it).

For the liveness probe, I think if the breakpoint suspends only the current thread there should be always another thread available to answer the liveness probe. Any modern IDE should give the option to choose to suspend the whole JVM (which might be necessary if you have to examine other threads e.g. for race time conditions) or only the thread on which the breakpoint is. A fix could be as simple as documenting this feature, recommending to use the suspend-on-thread-only.

> Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session
> ----------------------------------------------------------------------------------------------------------
>
>                 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.x
>
>
> 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.2.3#72005)