httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 21322] - main worker process locks up and no longer accepts requests
Date Sat, 12 Jul 2003 22:29:47 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21322>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21322

main worker process locks up and no longer accepts requests





------- Additional Comments From glenn@apache.org  2003-07-12 22:29 -------
Switching to the prefork worker is an option, but then we lose all the
benefits of the worker MPM.  In our testing we saw 30-50% reduction in
CPU usage and memory usage reduced to 15-20% from Apache 1.3 for the
same request volume.  :-)  prefork might be an option, at least we could
still use filters.  I am willing to stick with the worker MPM until we either
find a solution to the semaphore problem or the sysads where I work get tired
of getting paged once a week and lynch me. ;-)

In all cases where apache 2 has stopped accepting requests there were only
three httpd processes, the root process, the cgid daemon process, and
one child worker process, that single child worker process was hung trying 
to lock the accept mutex.

With regard to switching mutex types, how would I specify to configure
that I wanted to use native Solaris mutex's rather than posix?

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message