https://bz.apache.org/bugzilla/show_bug.cgi?id=55415
--- Comment #9 from Luca Toscano <[email protected]> --- (In reply to trenzterra from comment #8) > Hi, I have updated Apache to 2.4.5 which has this fix incorporated. It works > perfectly when I specify ProxyErrorOverride On and ErrorDocument 404 > /404.php for example. > > However, Apache2 still seems to crash with concurrent requests are sent. I > tried a stress test using JMeter with 300 concurrent queries over 3 seconds, > and after the first 10 threads my server seems to conk out. > > Meanwhile, if I point JMeter to a non-404 PHP page (which is proxied through > PHPFPM as well), I have no issues. > > Just wondering if error handling isn't as graceful as it seems? This sounds a bit strange, even if setting a 404.php page means effectively issuing two requests to the backend (the original php request that ends up in a 404 and the 404.php page itself). I have a couple of questions to expand the "conk out" description: 1) What is the server-status when you observe httpd not working anymore? Do you notice any weird change in process/threads state? 2) Which mpm are you running? What is the config used? 3) Anything useful in the error.log? (Maybe even increasing the log verbosity with LogLevel if you can - https://httpd.apache.org/docs/2.4/mod/core.html#loglevel). 4) Have you tried a more recent version of httpd to see if you are still able to reproduce? 2.4.5 is a bit old and it might carry performance problems that have been resolved during the recent years. Thanks! -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
