Menu
Does recycling the IIS7 application pool kill any currently executing requests? Or does it wait for all requests to complete (like a drain-stop)?
I don't want the recycling rules to cause intermittent errors from my WCF sites.
Thanks
714
What is application pool recycling in IIS? Recycling means that the worker process that handles requests for that application pool is terminated and a new one is started. This is generally done to avoid unstable states that can lead to application crashes, hangs, or memory leaks.
Worker process isolation mode offers process recycling, in which IIS automatically refreshes Web applications by restarting their worker processes. Process recycling keeps problematic applications running smoothly, and is an especially effective solution in cases where it is not possible to modify the application code.
As an aside you should schedule any application pool recycles to occur during off-peak hours, as you've realised it will clear any active sessions and will break the user experience if the application relies on session storage.
The IIS application pool for Taskmaster Web must be scheduled to recycle daily to ensure optimal system performance.
No.
By default, the WWW service establishes an overlapped recycle, in which the worker process that is to be terminated is kept running until after a new worker process is started.
This is from the Documentation for IIS6 and I am sure it applies for IIS7.
If your web service requests are long-running, you might consider increasing the shutdown timeout.
50
Yes. Recycling an application pool causes the WWW service to shut down all running worker processes that are serving the application pool, and then start new worker processes.
This is from the Documentation for IIS6 and I am sure it applies for IIS7
38
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
