Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: Process exiting because it reached MaxRequestsPerChild |
|
| Author |
|
zantoro
Joined: 05 Feb 2009
Posts: 9
|
 Posted: Wed 15 Jul '09 13:24 Post subject: Process exiting because it reached MaxRequestsPerChild |
 |
|
Hello,
we have set the MaxRequestsPerChild to 250 on our server to prevent server overload.
What are the downsides of this setting?
What happens to the website availability when the child is flushed as the MaxRequestsPerChild limit is reached (see the title)?
Thanks,
Roberto. |
|
| Back to top |
|
James Blond
Moderator
Joined: 19 Jan 2006
Posts: 7371
Location: Germany, Next to Hamburg
|
| Posted: Wed 22 Jul '09 17:43 Post subject: |
|
|
MaxRequestsPerChild shall prevent of memory leaks and shall kill unused child process when the traffic goes back.
Since windows has only one child apache will restart after reaching that limit. For windows it is recommend to leave that value to 0 so it runs unlimited.
See http://httpd.apache.org/docs/2.2/en/mod/mpm_common.html#maxrequestsperchild
Memory leaks under windows are only with third party module like PHP extension. But than it is recommend to separate PHP from apache with fcgid. (only if apache crashes) |
|
| Back to top |
|
|
|
|
|
|
