Disabling Application Pool

I'm trying to learn what causes application pool to be disabled based on the "Rapid-Fail  Protection" settings in IIS 6 and IIS 7.

What I'm really interested to know is how I can make app throw exceptions/errors that could disable application pool based on 1 error/failure in 1 minute threshold.

ASP.NET Run time errors, simple App Exceptions do not seem to bring the app pool down, but what could?

Thanks for your help

ExcUsr2008Asked:
Who is Participating?
 
ExcUsr2008Connect With a Mentor Author Commented:
thanks for your response, but no ... it would not assume the major glitch is with the system, but the application itself or its configuration.

Once again, "What I'm really interested to know is how I can make app throw exceptions/errors that could disable application pool based on 1 error/failure in 1 minute threshold."

One experiment I did was to simulate memory leak in the application and it did bring the application pool down (disabled). So I'm interested to know what kind of issues cause app pool to be disabled.

//This will eat up max memory allocated and cause IIS to disable the app pool that is hosting the application.
  List<byte[]> list = new List<byte[]>();
        while (true)
        {
            list.Add(new byte[1024*10]);
            System.Threading.Thread.Sleep(1);
        }
0
 
Carl TawnSystems and Integration DeveloperCommented:
If an app pool suffers a serious fault then IIS will recycle it. If IIS has to recycle the pool a specific number of times within a defined period then it assumes there is a major glitch with the system, or one of the applications in the pool, so it will disable the pool in order to maintain overall server stability.
0
 
Carl TawnSystems and Integration DeveloperCommented:
>> it would not assume the major glitch is with the system, but the application itself or its configuration.

Erm, yes it would! It assumes it's a recurring fault beyond the control of IIS to fix, which could either be a problem with the application or something on the system outside of the web app itself that causes the fault. A disk read failure could cause the app pool to recycle...which as far as IIS is concerned is a SYSTEM fault.
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
ExcUsr2008Connect With a Mentor Author Commented:
Thanks both for your responses and I agree disk read failure can cause worker process to be disabled, in fact the pool wont even start if there is a H/W issues, and that's all good.

But I believe my question is not answered yet. Again, I'm trying to find the types of "application failures", meaning bugs within the code that could cause IIS to disable the application pools. I even provided an example of code  (out of memory) in my previous response to to be clear in my question.

0
 
ExcUsr2008Author Commented:
Have not received proper answer to the question.

I've provided a partial answer as an example myself.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.