[Bug 62816] New: MaxConnectionsPerChild kills active connections
Bug ID: 62816
Summary: MaxConnectionsPerChild kills active connections
Product: Apache httpd-2
Target Milestone: ---
MaxConnectionsPerChild will kill any active connections/threads on the child
that reaches maximum connections.
Red Hat Enterprise Linux Server release 6.9 (Santiago)
Server version: Apache/2.4.35 (happens on older versions of 2.4)
PHP (only used for its sleep() function below)
Apache httpd.conf (yes the values are unreasonably low, but they more easily
demonstrate the problem. The problem still exists with reasonable values as
long as MaxConnectionsPerChild != 0):
How to reproduce (IE11 recommended, if not that then Chrome):
1. Access http://<yourserver>/test.php. It will spin while the sleep executes.
2. Open a new browser tab and access http://<yourserver>/anythingelse.
3. Both tabs will immediately show "Can't reach this page" or something
IE11 demonstrates this most effectively, with both pages down for the count.
In Chrome 69, the first tab will show ERR_EMPTY_RESPONSE but will attempt to
refresh itself and the second page doesn't show an error, just refreshing
Again, this isn't just because of the ridiculous httpd.conf above. The issue
still occurs with more servers, threads, etc. The issue just occurs
You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail: bugs-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: bugs-help@xxxxxxxxxxxxxxxx