Mailing List Archive

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

inf <info@dressmaker.ca> changed:

What |Removed |Added
----------------------------------------------------------------------------
OS|Linux |Windows Server 2008 R2

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

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

engrand <eraymond@tegona.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
OS| |All

--- Comment #2 from engrand <eraymond@tegona.com> ---
Did you find any solution ?

We have the same issue, our architecture is the following:

* apache run in foreground mode inside a docker container
* apache run behind haproxy with option forceclose
* Use of mpm_event with the following configuration:

StartServers 3
ServerLimit 16
ThreadLimit 32
MinSpareThreads 25
MaxSpareThreads 32
ThreadsPerChild 32
MaxRequestWorkers 512
MaxConnectionsPerChild 1024

Keepalive On

The number of children grows up until the limit then the server cannot serves
request anymore. With mpm_worker, the number of children grows up infinitely.
As consequences, the memory usage also grows up.
It seems, it is not the gracefully stop problem, because apache status does not
show a such situation.

As workaround, we just set MaxConnectionsPerChild to 0.

Thank you for your help.

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