I'm trying to understand exactly what this termination state means. I'm seeing
http connections from clients that seem to be complete and queued. These
requests seem to be timing out from the queue well before the "timeout queue"
time though. The proxy is busy at these times and there are a number of
requests queued.
Why are these sessions terminated? I was expecting it to be terminated after
the 30s "timeout queue" but it seems to have terminated after just 5s while
waiting for client data (which seems odd since the Tq value is present and
small). My understanding was that requests would not be queued until the
client completed sending the request.
Here is a sample log entry that shows the issue. This is using 1.3.20 btw.
111.222.333.444:1234 [08/Jan/2010:13:05:42.055] web portal/<NOSRV>
19/5000/-1/-1/5019 503 212 - - cQ-- 811/811/721/0/0 0/550 "GET /foo/bar
HTTP/1.1"
defaults
timeout connect 5s
timeout client 5s
timeout http-request 5s
timeout server 20s
timeout queue 30s
-Bryan
