What is the effect of stopping an AppPool on currently executing requests?

Question

It is my understanding that asking an AppPool in IIS to recycle will give currently active requests 90 seconds to complete before they are abnormally terminated by the recycle request, while no longer accepting new requests. What about asking an AppPool to stop? Does it too have the same spin-down policy?

If it matters, I'm stopping the AppPool via:

appcmd.exe stop apppool /apppool.name:"theAppPoolName"

Version: 10.0.14393.0
Server: Windows Server 2016 / IIS 10

score 5 · Accepted Answer · answered Jun 22 '17 at 07:49

5

Yes, stopping an AppPool (rather than killing its process) does also gracefully shut down the ApplicationPool, giving existing requests time to finish.

So the behavior is the same as for recycling the pool.

answered Jun 22 '17 at 07:49

Peter Hahndorf

13,763
3
37
58

You wouldn't happen you have a reference for this? – HiTech Nov 17 '18 at 05:49
@HiTech - not off top of my head, just many years of experience. – Peter Hahndorf Nov 17 '18 at 16:04

What is the effect of stopping an AppPool on currently executing requests?

1 Answers1