I am seeing this behavior too.
If I do a graceful-stop followed by a start on a system that I know is
getting no traffic, the old parent process sometimes hangs around for a bit
(I think for GracefulShutdownTimeout secs).
On a related note - If I do a graceful-stop followed by a start on
a heavil
I stopped load and waited for thrice as long as our application timeout.
On Thu, Aug 20, 2009 at 7:43 AM, Eric Covener wrote:
> On Thu, Aug 20, 2009 at 10:24 AM, Mohit Anchlia wrote:
>> I think I knew that. Question is even though there were no outstanding
>> requests the httpd servers stayed ther
On Thu, Aug 20, 2009 at 10:24 AM, Mohit Anchlia wrote:
> I think I knew that. Question is even though there were no outstanding
> requests the httpd servers stayed there until I finally killed them
How did you ensure that there were no outstanding requests?
--
Eric Covener
cove...@gmail.com
---
I think I knew that. Question is even though there were no outstanding
requests the httpd servers stayed there until I finally killed them
On Thu, Aug 20, 2009 at 3:09 AM, Apache Admin wrote:
> Hi,
>
> when u run graceful-stop , it will work in different manner
>
> Let see first it kill p
Hi,
when u run graceful-stop , it will work in different manner
Let see first it kill parent process if any child process serve
request.. it continue to server, but not accept new request ..new
request handle by new child process ... mean it will take a little bit
time t
I installed Apache 2.2.11 and tested graceful-stop. When I run
graceful-stop I still see all the httpd processes even though there is
nothing listening on port 80. Those httpd processes stay there even
though there are no incoming or existing sessions. Is there a bug
someone knows about or am I doi