kala-tamin Application pool recycle after “Fixed number of requests”

Application pool recycle after “Fixed number of requests”

What are the effects of IIS's app pool setting for recycling to recycle after "Fixed number of requests"?

Suppose this number is 100, and the 99th person connects to my web site, then the 100th person comes and will trigger an application pool recycle.

Does this mean all session information for sessions 1-99 will be lost (in-process session will expire when application pool worker process restarts)?

Get IIS Web Site identifier programmatically


ASP.Net error: The Local Security Authority cannot be contacted
You basically have it right, but it's not the person, it's the request.

How do I modify the custom errors of a remote IIS6 website using MSBuild
Each aspx page called on your application will add up and when the threshold is reached, the application pool is recycled, the application domain (if your using .Net) is unloaded and everything starts up again.

Server with Load Balancing is redirecting to wrong page
You lose Session, Application and any static variables laying around.

Bulk Create Websites in IIS 6.0 Management Console
If your using classic asp or php, every session and global variables are lost too..
How can I set global mime-types for IIS6 programmatically?
A number of hits threshold is a bit overkill.

IIS 6.0 Application Pool Identity Being Ignored
You should either disable it or set it to a huge number.

IIS6 - Users login and then get redirected to login page, have to reboot their PCs to break this loop, then fine
By default, if I recall well, the IIS6 application pool recycles every 15 minutes if there were no request and you can also put threshold on the total memory used by your application to trigger recycling..


That is quite correct.

If you do not use some kind of Session farm, or database backing of the session information, it will be lost when the application pool is recycled.

I would recommend trying hard to not require any session information - this will make your application more scalable and reliable as it maps more closely to the stateless nature of the underlying HTTP..

63 out of 100 based on 58 user ratings 683 reviews