[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24868: ------------------------------------------ If I get things right changing the router timeout seems non-available to the non-admin user. Then it seems as if we could forward the ports from the ports directly (not connecting via the router). I believe that this is what we're doing currently: {code:title=https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/org.jboss.tools.openshift.core/src/org/jboss/tools/openshift/core/server/behavior/OpenShiftLaunchController.java#L360} Set<PortPair> podPorts = PortForwardingUtils.getForwardablePorts(pod); {code} So far I believe that we're not affected by the timeout in the router. But then, it this scenario there's apparently a timeout in the port-forwaring, too, as discussed here: https://issues.jboss.org/browse/JBIDE-23422?focusedCommentId=13334141&.... In arquillian they add a keep-alive ping, something we cannot do since we use oc to forward the ports and thus are not in control of that socket. I believe that we should reach out to openshift for advice how to tackle this since it makes debugging pretty useless. [~rhuss] [~jeffmaury] [~aurelien.pupier] Thoughts? -- This message was sent by Atlassian JIRA (v7.2.3#72005)