[
https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-24868:
------------------------------------------
[~rhuss] [~aurelien.pupier] [~jeffmaury] Weird enough the latest CDK 3.1.1-1 doesnt seem
to respect the annotation. When using the nodejs-mongo-persisntent template and annotating
the route with
{code}
"metadata": {
"annotations": {
"haproxy.router.openshift.io/timeout": "1h",
{code}
the router would still respond with an "application is not available" after
~1min. It is as if the router would not change it's timeout. Prior CDKs were only
displaying this error after the timeout that I annotated the route with (see
https://issues.jboss.org/browse/JBIDE-24868?focusedCommentId=13457650&...)
!application-is-not-available.png!
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.AM3
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-livene...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)