No response from Apache2 at client

[dmfirst]

I am trying to uncover a problem that has materialised with an Apache2/Tomcat based application. The installation has been running without problem for a year, but recently a new web service has been added. As a result of this, the number of concurrent server requests that have to be dealt with has increased significantly. What happens is that when a batch of say 50 to 100 concurrent requests are sent to the server, one of them receives no response at all (i.e. nothing - no message from the server at all) whereas all the others are successful. An interesting part of the problem is that the failed request does not appear in the transfer logs at all. Any ideas on what would cause this to happen?

David Mellors
First Light Associates

http://www.firstlightassociates.co.uk

 

[cdeardor]

I assume you're using mod_jk or mod_jk2 to talk to tomcat. You may want to check your httpd.conf file for the following section...

# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

If you want to be sure, Change 100 to 0 and restart httpd.

 

[dmfirst]

Thanks, its currently set at 100, so I will try that. I can also confirm its using mod_jk as a connector. Might it be worth moving to mod_jk2?

David Mellors
First Light Associates

http://www.firstlightassociates.co.uk

 

[dmfirst]

It appears that the problem was to do with network configuration. A reengineering of the network for some other problem seems to have fixed this, as it has not failed testing since

David Mellors
First Light Associates

http://www.firstlightassociates.co.uk