[
https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi...
]
Jeff MAURY commented on JBIDE-24868:
------------------------------------
[~adietish] So far we have three problems:
# the timeout for the Java debug connection (and we use the port forwarding feature for
that)
# the timeout from the router (because the web browser is using the route)
# the pod get rescheduled because of the livenessprobe if Java debug is configured as
suspendVM on breakpoint (seems default on Intellij)
1) not sure we can fix it
2) can be solved by using the forwarded port for the pod instead of the route but we will
still get the same problem in the forwarded port but I think the timeout on the forwarded
port is probably larger that the one on the router so we will have the same status as 1)
3) can be solved by updating the deployment config
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.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-livene...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)