Forum Moderators: phranque
I work for a large insurance company, and we are running IBM HTTP Server 6.0.1 which from my understanding is powered by Apache 2. Now we recently had an issue where all our IHS Servers stopped responding to HTTP requests, the physical machines were up and running and we could Terminal Services to the boxes, and requests were being forwarded from the HTTP server to Apache Tomcat, however when trying "localhost" it just timed out. I did a netstat -a and greped for the Established connections and there were over 180 on port 80, I am assuming these are the number of threads to the web server.
I guess what I am asking is, if the server thread count is set to 250 as I think it is by default, would 180 odd threads be enough to cause it to stop responding to requests? I know it was responding to existing connections as I can see content being served in the access.log.
Then without a restart on anything the server began responding to requests, and did another netstat and found about 35 established connections on port 80.
Has anyone seen this behaviour before? do you know what can cause it, any help on this would be greatly appreciated.
Many thanks
Jo
