osdir.com


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug 62816] New: MaxConnectionsPerChild kills active connections


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

            Bug ID: 62816
           Summary: MaxConnectionsPerChild kills active connections
           Product: Apache httpd-2
           Version: 2.4.35
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mpm_event
          Assignee: bugs@xxxxxxxxxxxxxxxx
          Reporter: jb9244@xxxxxxx
  Target Milestone: ---

MaxConnectionsPerChild will kill any active connections/threads on the child
that reaches maximum connections.

OS version:
Red Hat Enterprise Linux Server release 6.9 (Santiago)

Apache version:
Server version: Apache/2.4.35 (happens on older versions of 2.4)
Event MPM
PHP (only used for its sleep() function below)

Setup

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):
===================
<IfModule event.c>
ServerLimit           1
StartServers          1
ThreadsPerChild       2
MaxConnectionsPerChild 2
</IfModule>
===================

PHP test.php:
===================
<?php
sleep(100);
===================

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
equivalent.

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
immediately.

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
sporatically.

-- 
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