I am trying to install Apache-1.3.23 with various third-party modules, including php/3.0.18 with the security patch to support the users who are already using php3.
As soon as I started using this web server in production, I noticed this problem with it. If the apache option "KeepAlive" is on (which is the default), the httpd processes do not timeout after they service their requests but keep on accumulating until the number of httpd processes reaches 150. At this point, httpd does not service any new requests because the max number of httpd processes has been reached. As soon as I disable the PHP3 module, the site works fine, with the average number of httpd processes below 30. The number of daily hits is slightly above 200,000. Almost no users use PHP3. I have searched google for a while to see if this is a known problem. I found only two or three people complaining about it but no real solution. Some apache developer suggested that this is a problem with php3 module because it much be catching the signal sent to httpd. I also found a patch that changes "SIGALRM" with "SIGUSR2" in apache source in a couple of places to fix this problem (http://bugs.apache.org/index.cgi/full/3906). Right now, I am running this httpd with KeepAlive option turned off but I'd like to get this problem fixed eventually. I could apply the patch above though it sounds like a kludge because the real problem is likely with PHP3. Does anyone else run php-3.0.18 with a recent version of apache on Solaris on a site that gets 100,000 or more hits per day? What did you do to make it work? -akop -- PHP Install Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
