On 29.04.2010 18:14, Greg Ames wrote:
I re-read this thread and see that we have a request in progress, so
this isn't RFC approved behavior. Sorry for the noise.
Hmmm, it depends. The situation observed and the discussion I raised is
about an established connection having already returned a Connection:
Keep-Alive and a response, waiting for the next request, and now a
process shutdown arrived via e.g.
- graceful-stop
or
- MaxRequestsPerChild reached
or
- MaxSpare detected during maintenance
Yes, in the observed situation the next request for the connection has
already been transmitted and ACKed, but not yet read by Apache. So from
the point of view of the web server it hasn't yet accepted the request
but it could find out whether there is one waiting to be handled, from
the point of view of the client the next request has been successfully
transmitted.
Regards,
Rainer
On Sun, Apr 25, 2010 at 2:07 PM, Rainer Jung <rainer.j...@kippdata.de
<mailto:rainer.j...@kippdata.de>> wrote:
On 23.03.2010 15:30, Jeff Trawick wrote:
Is that expected behaviour? It doesn't seem
reproducible for the worker
MPM.
The behaviour has been observed using extreme spare
rules in order to
make
processes shut down often, but it still seems not right.
Is this the currently-unhandled situation discussed in
this thread?
http://mail-archives.apache.org/mod_mbox/httpd-dev/200711.mbox/%3ccc67648e0711130530h45c2a28ctcd743b2160e22...@mail.gmail.com%3e
Perhaps Event's special handling for keepalive
connections results in
the window being encountered more often?
I'd say yes. I know from the packet trace, that the previous
response on the
same connection got "Connection: Keep-Alive". But from the
time gap of about
0.5 seconds between receving the next request and sending
the FIN, I guess,
that the child was not already in the process of shutting
down, when the
previous "Connection: Keep-Alive" response was send.
