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

Andre Dietisheim (JIRA) issues at jboss.org
Tue Aug 22 17:17:00 EDT 2017


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

Andre Dietisheim edited comment on JBIDE-24868 at 8/22/17 5:16 PM:
-------------------------------------------------------------------

[~rhuss] [~aurelien.pupier] if I understand the documentation right there seem to be no default for the lifenessProbe. There seem to exist 2 strategies to achieve such a probe: a freely custiomizable one and a http based approach. The http variant seem to have a freely definable url. I had a quick look at the nodejs-mongodb template and couldn't find such a check. 
What are we in tools supposed to do? Parse pods and find out if and what method is being used? Shouldnt we have settings in the docker image metadata?


was (Author: adietish):
[~rhuss] [~aurelien.pupier] if I understand the documentation right there seem to be no default for the lifenessProbe. There seem to exist 2 way to achieve it and the http approach having a variable url for the check. I had a quick look at the nodejs-mongodb template and couldn't find such a check. 
What are we in tools supposed to do? Parse pods and find out which method and what url are being used? Shouldnt we provide settings in the docker image metadata?

> Server adapter: Switch off livenessProbe.periodSecond property during debug session
> -----------------------------------------------------------------------------------
>
>                 Key: JBIDE-24868
>                 URL: https://issues.jboss.org/browse/JBIDE-24868
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: openshift
>            Reporter: Aurélien Pupier
>            Assignee: Andre Dietisheim
>            Priority: Critical
>              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)



More information about the jbosstools-issues mailing list