IIS 7 and Above
Application Initialization Module
Is this a detructive on non-destructive process?
Last post Nov 29, 2015 08:49 PM by BrockAllen
Nov 29, 2015 02:15 PM|ojking|LINK
Recently I found myself in a quandary. I have worked on IIS in all its variations now for over 15 years. I will never claim I know it all (a certain means of learning humility), but I have developed a pretty good knowledge-base. Nevertheless, I have come
to question my personal assessment. Here is the dichotomy:
I have always preached that an application pool recycle is a non-destructive process. When you recycle, the old pool stops accepting new threads and a new app pool is spun up to accept new threads. The crux is, I have always believed that the old pool
gracefully shuts down and does not hard kill the remaining threads. Today I was challenged on that point and had someone from Microsoft quoted as specifically stating that unless the threads dissipate quickly, they will be hard killed, that there is no graceful
While things went far afield from there, this is a pivotal issue. Is a recycle of any app pool destructive or non-destructive? If the threads in the old pool face a hard kill, the process is destructive. If there is no graceful shutdown, then destructive!
I always thought this was the edge IIS had over J2EE. Can someone settle this?
Nov 29, 2015 08:49 PM|BrockAllen|LINK
There is a window of time given to shutdown an apppool, after which it does become destructive. I don't recall what it is exactly, but I have a fuzzy memory of it being like 90 seconds.