[
https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-24868 at 10/3/17 11:33 AM:
--------------------------------------------------------------------
weird enough, an app based on eap64-basic-s2i is respecting the timeout, i dont see a
"bad gateway" error happening here if I halt the code in some breakpoint.
Once the bad gateway error is displayed in the browser, the debug connection is cut and
the debugger thread is terminated in Eclipse.
* No new pod is respun in OpenShift when this happens.
* Neither nodejs-mongo-persistent- nor eap64-basic-s2i-templates have lifeness probes.
was (Author: adietish):
weird enough, an app based on eap64-basic-s2i is respecting the timeout, i dont see a
"bad gateway" error happening here if I halt the code in some breakpoint.
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)