[
https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi...
]
Jeff MAURY commented on JBIDE-24868:
------------------------------------
I tried with the nodejs builder images (not the persistent one) and did not experience the
problem. I think this is because the persistent template defines a livenessProbe and as
the nodejsVM is mono threaded because it is blocked in the breakpoint the liveness check
then fails and OpenShift kills the pod.
So from the route timeout POV, this is ok for me
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.Final
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.5.0#75005)