Bug 47528 - Worker process won't restart more than once using MaxRequestsPerChild with mpm_winnt
Summary: Worker process won't restart more than once using MaxRequestsPerChild with mp...
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mpm_winnt (show other bugs)
Version: 2.2.9
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2009-07-14 13:32 UTC by John McCaskey
Modified: 2018-11-07 21:08 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description John McCaskey 2009-07-14 13:32:09 UTC
I'm using Apache 2.2.9, but I didn't find any changes in the newer versions that appear related to this issue.  I've set MaxRequestsPerChild to 500 in my Apache config.  If I watch the server-status page and refresh 500 times I see the PID for the process change and in my logs I see that the server restarted due to hitting hte max.  If I repeat this and go to 1000 requests no restart occurs, no matter how many more requests are issued the process doesn't restart.

This is a problem for us because the process seems to use more and more memory over time and since there is only a single process on Windows we are stuck with only 2 gigs to share between all the threads and our PHP code running on the server can tend to use lots of memory.  We end up with PHP running out of memory after the server has been up for a while and have to manually restart it.  I wanted to just use the MaxRequestsPerChild to gurantee we'd restart a couple times a day, but that isn't possible due to this bug.
Comment 1 William A. Rowe Jr. 2018-11-07 21:08:22 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.