You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/02/28 16:30:40 UTC
DO NOT REPLY [Bug 16241] -
Apache processes takes 100% CPU until killed manually
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=16241>.
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=16241
Apache processes takes 100% CPU until killed manually
stephanandreas.rickauer@eds.com changed:
What |Removed |Added
----------------------------------------------------------------------------
URL| |http://sos.ethz.ch/~stef/typ
| |o3/
------- Additional Comments From stephanandreas.rickauer@eds.com 2003-02-28 15:30 -------
I experience the same effect, but without having something in the logfile. The
effect only seems to occur, when one client requests data from one slot over a
long time. We tested with 12 hits/min at 1.9 pageviews/min constant traffic from
one Loadrunner machine to different php pages. After 9 hours the first child
used 100% CPU. After another 1.5 hour, the second child went crazy, each using
50% CPU. This effect went on and does not stop when stopping the load until I
kill the crazy children. I have the analysis data online at
http://sos.ethz.ch/~stef/typo3/
My Apache is 1.3.23 with mod_php 4.1.0, SuSE8.0, Kernel 2.4.18-4GB
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org