https://bz.apache.org/bugzilla/show_bug.cgi?id=53555
--- Comment #16 from [email protected] --- This is certainly a bug and not a configuration issue. I have had this error happen with the default (Debian) configuration and other people online report the same. I have had this happen with mpm_event and mpm_worker. It's very reproducible. It happens with almost any thread related settings I have tried. It stops new requests from being served and is a serious problem. There is some bug with the way Apache handles its servers/threads. This is not something that can be fixed by tweaking the configuration. At best it might be mitigated by setting: StartServers 1 ServerLimit X ThreadsPerChild XXX ThreadLimit <ThreadsPerChild> MaxRequestWorkers <ServerLimit * ThreadLimit> MinSpareThreads <MaxRequestWorkers> MaxSpareThreads <MaxRequestWorkers> MaxRequestsPerChild 0 In other words, make it so a thread stays alive forever and therefore the buggy part of the code that is responsible for killing and reusing threads is never hit. Of course this requires always using the maximum amount of RAM since threads never die even when there is no traffic. -- 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]
