Mailing List Archive

https://bz.apache.org/bugzilla/show_bug.cgi?id=65592

Bug ID: 65592
Summary: mpm_event does not create new child after
MaxConnectionsPerChild is hit
Product: Apache httpd-2
Version: 2.4.49
Hardware: PC
OS: Linux
Status: NEW
Severity: regression
Priority: P2
Component: mpm_event
Assignee: bugs@httpd.apache.org
Reporter: matt.zuba@goodwillaz.org
Target Milestone: ---

I've encountered issues on multiple servers running Apache 2.4.49 where we have
MaxConnectionsPerChild set for the event mpm. When child processes die after
this limit his hit, the mpm is not creating new processes which stop Apache
from serving any requests. This issue did not exist in 2.4.48.

The easiest way for me to reproduce with the most simplistic example is with
the httpd docker images. When modifying the mpm_event conf and setting all
values to 1 (for ease of testing), 2.4.49 will cease to serve any requests,
whereas 2.4.48 will continue to serve request after request.

=====================
<IfModule mpm_event_module>
StartServers 1
MinSpareThreads 1
MaxSpareThreads 1
ThreadsPerChild 1
MaxRequestWorkers 1
MaxConnectionsPerChild 1
</IfModule>
=====================

I can produce some repos with Dockerfiles in them if necessary.

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org