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

[Andre Dietisheim (JIRA)]

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

Andre Dietisheim edited comment on JBIDE-24868 at 9/1/17 10:50 AM:
-------------------------------------------------------------------

[~aurelien.pupier] [~rhuss] Setting the router timeout via the annotation described above works for me. The router wont timeout any more and there's no "504 Gateway timeout" error being displayed any more. But then the Eclipse browser gives up, saying that the page could not be loaded. The external (Chrome MacOS) browser doesnt seem to bother, it keeps waiting. But then the debug session in Eclipse gives up and terminates once you have it continue after the breakpoint (F8).
So we should make sure that we respect the preferences where the user chooses to use an internal or external browser and go for this, agree?

* Without timeout setting in the router, default 1 minute timeout applies: 
Browser displays 504 Gateway timeout after a minute
https://youtu.be/J6pmzVBgbnk

* AnnotatingWithout timeout setting in the router, default 1 minute timeout applies:
Internal Eclipse browser pops up a dialog saying that it could not load the page. My external chrome didnt come up with such a message, it just kept waiting for several minutes (didnt wait until the end):
https://youtu.be/KzxDvgm5kF4



was (Author: adietish):
[~aurelien.pupier] [~rhuss] Setting the router timeout via the annotation described above works for me. The router wont timeout any more and there's no "504 Gateway timeout" error being displayed any more. But then the Eclipse browser gives up, saying that the page could not be loaded. The external (Chrome MacOS) browser doesnt seem to bother, it keeps waiting. But then the debug session in Eclipse gives up.
So we should make sure that we respect the preferences where the user chooses to use an internal or external browser and go for this, agree?

* Without timeout setting in the router, default 1 minute timeout applies: 
Browser displays 504 Gateway timeout after a minute
https://youtu.be/J6pmzVBgbnk

* AnnotatingWithout timeout setting in the router, default 1 minute timeout applies:
Internal Eclipse browser pops up a dialog saying that it could not load the page. My external chrome didnt come up with such a message, it just kept waiting for several minutes (didnt wait until the end):
https://youtu.be/KzxDvgm5kF4


> 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.1.AM2
>
>         Attachments: breakpoint-suspend-thread.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.2.3#72005)