Hi Stefan,

On Thu, Jan 30, 2014 at 09:46:12AM +0100, Stefan Majer wrote:
> Hi Willy,
> 
> we see the same effect in our environment here as well.
> We are not sure if this is related to a still open Websocket connection.
> 
> Do you think that a
> 
> timeout tunnel  1h    # timeout to use with WebSocket and CONNECT
> 
> in the configuration will help to terminate these processes after the
> specified timeout.

It's not exactly this. The timeout will ensure that dead or idle
connections will eventually get killed. But active connections will
not be killed as long as there is traffic flowing on them.

Haproxy only quits after the last session terminates. So for sure,
if it is maintained alive because of dead connections, this will
help. But if there is regular traffic on active connections, it
will not be enough.

Regards,
Willy


Reply via email to