On 06.03.2009 00:44, Ian Long wrote:
Here is some sample output from the system-status:
Srv PID Acc M CPU SS Req Conn Child Slot Client VHost Request
0-0 2096 0/50/50 _ 0.01 23 2 0.0 0.09 0.09 X web1.opterus.com GET
/lbcheck.faces HTTP/1.0
1-0 2097 0/12/12 W 0.01 513 0 0.0 0.05 0.05 X web1.opterus.com GET /
HTTP/1.1
2-0 2098 0/24/24 W 0.00 450 0 0.0 0.01 0.01 X web1.opterus.com GET
/login.faces HTTP/1.1
3-0 2099 0/39/39 W 0.01 207 0 0.0 0.06 0.06 X web1.opterus.com GET /
HTTP/1.1
4-0 2100 0/11/11 W 0.00 518 0 0.0 0.01 0.01 X web1.opterus.com GET /
HTTP/1.1
5-0 2101 0/31/31 W 0.00 271 0 0.0 0.06 0.06 X web1.opterus.com GET /
HTTP/1.0
The 'Get /' is from my data center provider, it's a piece of monitoring
software, but it looks like it doesn't wait for a response, because the
processes
are stuck in writing, and apache doesn't seem to realize the connection
is gone, as you can see some of the SS times are over 10 minutes, which
is longer than
all my timeout settings...
Is there any way to make apache realize the connections are gone? I will
talk to the provider about what they see on their end....
"W" is not necessarily writing, it could also be waiting for Tomcat to
produce an answer. If I remember it correctly, you also send "/" to Tomcat.
Thos probe-but-not-wait requests could well be responsible for the
client abort log messages.
Usually once the web server tries to write back the first response
packet, and the client has already closed or reset the connection, the
web server will note this immediately.
So somehow I suspect, that those requests are still waiting for the
result form the backend.
Is it just those few? What are the other 100-200 httpd processes doing?
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
