Arun, This is just a WAG, but I think that the problem still lies in
the client side and how the load balancer is handling the requests. I
would still be interested in seeing the netstat -atunep output from one
of he affected machines when there is a high level of connections in a closed
state. Even though the sessions aren’t sticky, is it possible that
the load balancer is handling keep alive in such a way that it’s sending
the back to the original server but on in a new state? (that’s a little
beyond my knowledge though). Gary Smith From: Arunkumar
Janarthanan [mailto:arunkumar.webadmin@xxxxxxxxx] Thanks Gary,
IP port
Type State Req/s 731-...30_80 x.x.x.x
80
HTTP
UP 16/s 731-...31_80 x.x.x.x
80
HTTP
UP 16/s 731-...31_80 x.x.x.x
80
HTTP
UP 14/s 731-...55_80 x.x.x.x 80
HTTP
UP 20/s
Rsp/s Reqb/s Rspb/s ClntConn SvrConn
MaxConn SurgeQ 731-...30_80 16/s 12406/s
345117/s
7 285
0 0 731-...31_80 16/s 10956/s
365025/s
7 262
0 0 731-...31_80 14/s 11140/s
368655/s
6 268
0 0 731-...55_80 20/s 14322/s
420105/s
7 272
0 0 However
the Apache server status still shows the number of requests being handled huge
difference. I
have attached the balancer-manager page as well with this email. Best
Regards, Arun
J
|