Prev: Service Unavailable
Next: Component Based URL Rewrite
From: Chris M on 27 Jan 2010 15:58
Hi there,

Can anyone explain why an application pool recycle should cause an
upload to fail? I thought that when an app pool was recyled, the old
worker process completed its current requests before shutting down (or
hitting the shutdown time limit).

That seems to be the case for downloads (i.e. I can start a very large
download from IIS and force a recycle of the app pool, and the worker
process doesn't exit until my download has finished), but recycling an
app pool during an upload causes the connection to be reset immediately.

Any advice?

Thanks,

--
Chris M.
From: Krishna on 4 Feb 2010 04:43
on the same note, i have question, when a app pool recycle happens, will the
new request to the server will be queued or will IIS throw exception stating
"Thread is being aborted".

Thanks

"Chris M" wrote:

> Hi there,
>
> Can anyone explain why an application pool recycle should cause an
> upload to fail? I thought that when an app pool was recyled, the old
> worker process completed its current requests before shutting down (or
> hitting the shutdown time limit).
>
> That seems to be the case for downloads (i.e. I can start a very large
> download from IIS and force a recycle of the app pool, and the worker
> process doesn't exit until my download has finished), but recycling an
> app pool during an upload causes the connection to be reset immediately.
>
> Any advice?
>
> Thanks,
>
> --
> Chris M.
> .
>
 | 
Pages: 1
Prev: Service Unavailable
Next: Component Based URL Rewrite