httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oliver Schoett <>
Subject [users@httpd] Re: 2.2.13 mod_proxy: backend connection reused long after ttl expired
Date Wed, 11 Nov 2009 12:08:42 GMT
Oliver Schoett wrote:

> It appears that the Apache 2.2.13 connection timeout (ttl) does not work.

Some more info:  the backend server sends a "TLSv1 Encrypted Alert" 
spontaneously when a connection is idle for approx. 17s.  The error in 
the log file (with a 502 error code sent to the client) occurs when this 
alert happens in response to another request being sent over the 
connection after approx. 17s idle time.  We even set ttl=5 now and still 
see these events.

How is it possible that a backend connection is reused after 17s idle 
time when ttl=5 and smax=0 in the ProxyPass configuration line?  Could 
this be a bug?

The hypothesis that some other processing within Apache or the client 
communication might have taken a long time and thus caused a delay is 
ruled out by the observation that the preceding response on the backend 
connection was transmitted to the client immediately (i. e., 17s ago), 
and the request causing the error was received immediately before the 
error event.


Oliver Schoett

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message