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=34664>. 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=34664 ------- Additional Comments From [EMAIL PROTECTED] 2006-12-21 11:03 ------- Hello everyone, I'd like to report that this particular bug is affecting us as well. We have two identical web servers running (using load balancing): Dell, Win2003 Web Edition, 2.8 Ghz, 2 GB memory Apache 2.2.3, OpenSSL 0.9.8d Tomcat 5.5.17 PHP 5.2, Zend Optimizer 3 We used to run IIS for over 4 years, but we've always had problems with the IIS->Tomcat integration. This September we switched to Apache and also started using PHP. I had to apply the "Win32DisableAcceptEx / EnableMMAP off / EnableSendfile off" trio, without it, same errors as mentioned above kept appearing in the error log, and the users got Page Not Found errors. After applying these settings, everything seemed fine. There's no firewall software running, but there is a Sonicwall firewall on the network. After applying Win32DisableAcceptEx, then "FATAL: erealloc(): Unable to allocate XXX bytes" lines immediately started appearing. I did a lot of searching, assuming the problem was with PHP. (5.1.6 did the same thing. We have some pages that are encoded, so we needed the new Zend Optimizer too before we could upgrade to 5.2. It's now out, we upgraded, same problem.) I wrote a small program to monitor and log the memory taken up by httpd.exe, and I found that it restarted itself about every 4-5 hours, when it reached around 440Mb. Then I finally found this thread, and the suggestion of the original poster worked. "ThreadsPerChild" was 250 in httpd.conf, I reduced that to 120, and it was fine. The service was 100% up! However, our sites became slow, we're getting about 100 requests per second. We tried to increase the number of threads. With 150 it still died every 4-5 hours. With 135 too. Now it's on 128, and it's been stable for almost a day. That's way too low however, the servers should be able to handle a lot more than that. I understand that this problem will be very hard to track down and fix... I'm still not even 100% convinced that it's an Apache problem, could be PHP. Still I hope someone will be able to figure this out and put out a fix. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
