[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23422 at 11/16/16 1:03 PM: -------------------------------------------------------------------- [~jcantrill] thx, I was pointed to the same PR and if I read it carefully I see the following options that we can set to the env vars of the deployment config: {quote} `*ROUTER_DEFAULT_CLIENT_TIMEOUT*`| 30s | How long a client has to acknowledge or send data. `*ROUTER_DEFAULT_CONNECT_TIMEOUT*`| 5s | The maximum connect time. `*ROUTER_DEFAULT_SERVER_TIMEOUT*`| 30s | How long a server has to acknowledge or send data. `*ROUTER_DEFAULT_TUNNEL_TIMEOUT*` | 1h | How long to allow TCP or WebSocket connections to remain open. {quote} So when enabling debugging we should be able to alter the deployment config of the router? was (Author: adietish): [~jcantrill] thx, I was pointed to the same PR and if I read it carefully I see the following options that we can set to the env vars of the deployment config: {quote} `*ROUTER_DEFAULT_CLIENT_TIMEOUT*`| 30s | How long a client has to acknowledge or send data. `*ROUTER_DEFAULT_CONNECT_TIMEOUT*`| 5s | The maximum connect time. `*ROUTER_DEFAULT_SERVER_TIMEOUT*`| 30s | How long a server has to acknowledge or send data. `*ROUTER_DEFAULT_TUNNEL_TIMEOUT*` | 1h | How long to allow TCP or WebSocket connections to remain open. {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)