By arsenalist
via arsenalist.com
Published: Nov 06 2007 / 18:46
How would you dig it if someone randomly restarted your application every few minutes or so for absolutely no reason? Would you be upset, angry or plain confused on why an application server would bother recycling an application at seemingly random intervals without being prompted. See, just like the Servlet specification defines the ServletContextListener interface, it’s .NET counterpart happens to be Global.asax which defines application lifecycle methods like Application_End, Application_Start and such. A pretty sensible idea when you look at the surface of things but what’s horribly, horribly wrong is that......
Comments
FlySwat replied ago:
Absolute FUD nonsense.
First of all, you can easily set when you want the application pool to recycle within IIS.
Second, the process only recycles if the server has been sitting dormant. This means your not going to have it recycle while someone is using it, which means that you will not lose any important session data. If you are storing data in sessions that you want to persist for long spans of time then you are a poor architect, regardless of what server you are using. Long term data should not ever be stored in sessions.
FlySwat replied ago:
Perhaps the author should bother to read how recycling actually works
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/24e3c22e-79a9-4f07-a407-dbd0e7f35432.mspx?mfr=true
Or how to configure it
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/1eee28e2-b319-4b4e-8267-a8c0aa0dcf36.mspx?mfr=true
Or how many enterprise sized setups [including ours] uses recycling to our advantage
http://blogs.technet.com/mscom/archive/2006/10/25/yes-we-recycle-that-includes-apppools.aspx
evarlast replied ago:
not to mention this has VERY little to do with IIS and everything to do with ASP.NET worker processes.
the same concepts apply to Cassini, mod_mono, and XSP
Voters For This Link (8)
Voters Against This Link (6)