This is the mail archive of the
mailing list for the Cygwin project.
Problem with accept?!! (was: Re: apache cygwin package hangs when MaxRequestsPerChild reached!)
- From: "Christopher B. Liebman" <liebman at zod dot com>
- To: <cygwin at cygwin dot com>
- Date: Sun, 1 Jun 2003 16:17:06 -0700
- Subject: Problem with accept?!! (was: Re: apache cygwin package hangs when MaxRequestsPerChild reached!)
- References: <006101c32799$b7fbd500$0401010a@XYZZY>
Ok, after some investigation I am starting to think that the issue is with
the behavior of accept(). When the apache main forks off its pool of worker
procs, each one calls accept() on the socket file descriptor. What I have
found is that when the first process in the pool exits (usually due to the
max requests being reached) ***none*** of the other pool process return from
accept() when the next request comes in on the socket. If I kill off the
current pool procs the *first* new one will respond to requests untill the
max is recieved again then as before, non of the other pool procs return
from accept. Any ideas on how to deal with this?
----- Original Message -----
From: "Christopher B. Liebman" <firstname.lastname@example.org>
Sent: Saturday, May 31, 2003 10:26 AM
Subject: apache cygwin package hangs when MaxRequestsPerChild reached!
> It seems that there is a bug somewhere in the server pool handling in
> under cygwin, When MaxRequestsPerChild is reached it hangs! Repeat by
> setting MaxRequestsPerChild to 5 and making sequental requests... the
> times out. I'm running the latest cygwin and the cygwin apache package.
> server pool config is:
> MinSpareServers 4
> MaxSpareServers 10
> StartServers 5
> MaxClients 150
> MaxRequestsPerChild 5
> Anyone have any ideas?
> -- Chris
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Problem reports: http://cygwin.com/problems.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html