I would start with the apache logs and find out what kind of requests
are logged in the access just before the event. That should get you
going in the right direction.
--David
Lars George wrote:
Hi,
We have an odd problem we cannot solve. Maybe someone else has come
across this too.
We use Apache 2.0.52 with the Tomcat 5.0.25 and its included mod_jk2
with Coyote/JK2 AJP 1.3 connector.
Usually Apache uses 230 slots out of 1000 it has set as the maximum.
This can be seen from the server-status page, it equals to say 32
requests per second.
Then all of sudden the Apache runs full and exceeds all empty slots,
ie. goes up to 1000 requests currently being processed and accepts no
further connections. All but a handful of these slots are in state
"W". Looking at the URI's the requests are both static content (like
images) served directly by Apache, but of course many requests are to
the dynamic content created by the app server (Tomcat).
I do not think this is a load issue per se, ie. where we have someone
hammering us with requests, since looking at the connections and URL's
they are all so random but valid at the same time that I do not think
this is it.
What puzzles me more is that they are all in the state "W". which
means "sending reply". The network seems to be OK at that point of
time too since I can connect to the machines no problem.
Only if I restart Apache by ultimately killing (killall -9 httpd) all
processes I can revive the site. After the Apache restart everything
goes back to normal right away. This seems to mean something too, at
least that it seems to be getting stuck somehow but whatever caused it
does not seem to exist anymore. Like something short, for example a
specific request, caused this.
What could I check from here? I cannot take the Apache out since we
need it for rewriting and session handling.
Any help or pointers are greatly appreciated.
Thanks,
Lars
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
