what happens to requests inside apppool when apppool crashes?

hi,

i have the following question: let us assume that my application pool in iis
6.0 has crashed due to i.e. faulty isapi filter. what happens to all the
requests already "handled" inside this apppool, but not "re-delivered" to
http.sys? will http.sys hands-over these un-answered requests to the recycled
apppool? or will these requests "die"? if they die, what error message is
sent back to the clients - 503 / service unavailable?

thanks in advance, fritz
--
Fritz Theiss

Re: what happens to requests inside apppool when apppool crashes?

On Nov 15, 1:20 pm, Fritz Theiss
wrote:
> hi,
>
> i have the following question: let us assume that my application pool in iis
> 6.0 has crashed due to i.e. faulty isapi filter. what happens to all the
> requests already "handled" inside this apppool, but not "re-delivered" to
> http.sys? will http.sys hands-over these un-answered requests to the recycled
> apppool? or will these requests "die"? if they die, what error message is
> sent back to the clients - 503 / service unavailable?
>
> thanks in advance, fritz
> --
> Fritz Theiss


The other requests in the worker process die. HTTP.SYS will detect the
crash of the worker process and log those requests as
"Connection_Abandoned_By_AppPool", which usually end up being detected
as connection timeout by the clients since no data is returned by
HTTP.SYS.

If the crash happened very rapidly, it could change the state of the
Application Pool to Rapid Fail Protection, at which point HTTP.SYS
will log and return 503 Service Unavailable.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//