[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24868 at 8/30/17 8:45 AM: ------------------------------------------------------------------- * *Router timeout*: according to the [docs|https://docs.openshift.org/latest/install_config/configuring_routing...] one can override the global timeout for a specific route by annotating it: {code} { ... "kind": "Route", "metadata": { "annotations": { "haproxy.router.openshift.io/timeout": "1h", {code} Using oc one has to do {code} # oc annotate route myroute --overwrite haproxy.router.openshift.io/timeout=2s {code} As a non-admin user I can process this change and it seems effective. This is a change that we could apply to the route when debugging, removing it once we stop the debugging. * *Debug connection timeout*: Doing a keepalive-ping within the debug connection as arquilian does seems not to be possible for us since we're not in control of the sockets that are used for this sake. * *lifeness probe*: this seems like an edge case, not critical. I ack though that with a lifeness probe in place debugging gets annoying since the user would have to manually remove it before and add it back in after debugging. [~jeffmaury], [~rhuss], [~aurelien.pupier] Thoughts? was (Author: adietish): * *Router timeout*: according to the [docs|https://docs.openshift.org/latest/install_config/configuring_routing...] one can override the global timeout for a specific route by annotating it: {code} { ... "kind": "Route", "metadata": { "annotations": { "haproxy.router.openshift.io/timeout": "1h", {code} Using oc one has to do {code} # oc annotate route myroute --overwrite haproxy.router.openshift.io/timeout=2s {code} As a non-admin user I can process this change and it seems effective. This is a change that we could apply to the route when debugging, removing it once we stop the debugging. * *Debug connection timeout*: Doing a keepalive-ping within the debug connection as arquilian does seems not to be possible for us since we're not in control of the sockets that are used for this sake. * *lifeness probe*: this seems like an edge case, not critical. I ack though that with a lifeness probe in place debugging gets annoying since the user would have to manually remove it before and add it back in after debugging. [~jeffmaury], [~rhuss], [~aurelien.pupier] Thoughts? -- This message was sent by Atlassian JIRA (v7.2.3#72005)