How to keep ASP.NET assemblies in AppDomain alive?

by

In IIS 6, go to the Application Pools section, and right-click > Properties on the pool which hosts the ASP.NET application in question. Go to the Performance tab and uncheck “Shutdown worker processes after being idle for:”

In IIS 7, go to the Connections pane and find Application Pools, and select Advanced Settings for the pool which hosts your application. Find the “Idle Timeout” property and set it to “0” (this disables it).

The default is 20 minutes of inactivity. By unchecking the box, once your AppDomain is loaded by the worker process, it will never die (unless you kill the process or something of course). By default, IIS will recycle the process when it reaches some limit, such as a memory cap, but it will also start a new one and “phase over” all incoming requests until the old one is unused, so as to minimize disruption.

I’ve also written a small c# class which will keep your ASP.NET application alive (alternate archived version) under normal circumstances. Since it runs within the application, obviously it can’t stop IIS or anything else from explicitly killing the process, but it will keep the application “hot”, e.g. the app will never go idle long enough for IIS to decide to shut it off.

If you do not have direct control over your IIS configuration (shared host, for example) your best bet is to have a small application running on a separate system – say, an always-on workstation – which hits your site every x minutes to keep the application pool from timing out. Nothing fancy – a simple WebRequest and a while() loop in a console application will do.

More Related Contents:

  1. What causes an application pool in IIS to recycle?
  2. ASP.NET restarts when a folder is created, renamed or deleted
  3. What is an IIS application pool?
  4. Maximum request length exceeded.
  5. Deploying website: 500 – Internal server error
  6. I just discovered why all ASP.Net websites are slow, and I am trying to work out what to do about it
  7. What is the difference between ‘classic’ and ‘integrated’ pipeline mode in IIS7?
  8. Asp.NET Web API – 405 – HTTP verb used to access this page is not allowed – how to set handler mappings
  9. How to increase request timeout in IIS?
  10. asp.net – session – multiple browser tabs – different sessions?
  11. How to prevent an ASP.NET application restarting when the web.config is modified?
  12. ASP.NET 4.5 MVC 4 not working on Windows Server 2008 IIS 7
  13. What are the (dis)advantages of using Cassini instead of IIS?
  14. IIS URL Rewrite and Web.config
  15. ASP.NET: HTTP Error 500.19 – Internal Server Error 0x8007000d
  16. How to deploy an ASP.NET Application with zero downtime
  17. How do I fix the “compilerVersion” IIS error?
  18. How to disable caching of single page application HTML file served through IIS?
  19. how SameSite attribute added to my Asp.net_SessionID cookie automatically?
  20. What is Kestrel (vs IIS / Express)
  21. Slow first page load on asp.net site
  22. What are the pros and cons of running IIS as 32bit vs 64bit on a 64bit OS?
  23. How to deploy ASP.NET MVC 4 application using localDB to local IIS on Windows 7?
  24. How do I Configure IIS to accept POST requests?
  25. “This operation requires IIS integrated pipeline mode.”
  26. Make MSDeploy (Visual Studio) not delete App_Data folder but delete everything else
  27. User ASP.NET runs under
  28. Maximum default POST request size of IIS 7 – how to increase 64kB/65kB limit?
  29. 404 Redirecting for non aspx pages
  30. IIS AAR – URL Rewrite for reverse proxy – how to send HTTP_HOST

Leave a Comment