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 41590] - Exceed Serverlimit directive when mod_php are using
Date Sun, 11 Feb 2007 17:45:44 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41590>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=41590





------- Additional Comments From fly-away@user.i.zabor.com  2007-02-11 09:45 -------
>It seems that the PHP requests aren't finishing, which triggers the growth in
processes.

I think it so, but isn't must apache kill his old child follow ServerLimit 
directive?

>You hit MaxRequestsPerChild or MaxSpareThreads, but because the PHP
>request is still running the child process can't actually exit.

Is this normal? 
I think, catching all bugs in apache modules (special in mod_php) match more 
hard task then implementation mechanism of harsh killing old child. 


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message