Thanks for the reply, in my case thread would hang like
WWCCWWWCWWWCWWWWWWWWWWWWCWWWCWCW
for 70 minutes and more till apache is restarted. No load is
generated, only RAM is consumed and the workers. All requests are
hitting PHP, but there is no way PHP would run more than 5 seconds,
it's configured and the holes allowing users to reconfigure timeouts
are patched. It just hangs in the midair, like waiting for a mutex
that won't ever open.
I don't know how to backtrace apache threads yet but I understand what
you mean and will give it a go when another such case happens. I can't
reproduce the faulty conditions. It just would eat threads out, for no
particular reasons.
It looks like there is always a new way to bring it down.
JT> W doesn't necessarily mean httpd is actively sending the reply. The
JT> request has been read and (generally) control has been passed to a
JT> module to generate and control sending of the reply.
JT> Backtraces of these threads would show where processing has hung.
JT> ---------------------------------------------------------------------
JT> The official User-To-User support forum of the Apache HTTP Server Project.
JT> See for more info.
www.rol.ru
Best regards,
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
| Article list | Name | Date |
| Click Here | Igor Franchuk |
||
| Click Here | Jeff Trawick |
||
| Currently Viewing : This Article | Igor | 2010-02-08 20:50:30 |