Skip to main content

IIS 7 Rapid Fail Protection - 5 failures within 5 minutes

IIS 7 Rapid Fail Protection

Thursday, January 12, 2012 by 
IIS 7 Rapid Fail Protection
If you do not already know, Rapid Fail Protection is feature within IIS7 that is on by default.  It basically is there to check for a specified number of hard failures in a given time period, again the default is 5 failures within 5 minutes.  If a hard failure that occurs meets this default setting, then the Application Pool will crash and does not automatically restart.  The only way to get it going again is to manually start it. 

If this does happen for you, in IIS Manager you would see a little stop symbol next to the name and it would also say stopped under Status (depicted below).
iis7

When this sort of problem occurs an entry is written to the Event Logs (usually under System), which IIS 7 does a little better of a job properly reporting errors.  You will most likely also get a 503.2 - Service unavailable error when trying to access the Application Pool. 

Personally I think this is a great feature, if it did not exist a broken application/service could crash > restart > crash > restart etc.. taking up all your system resources.  This Rapid Fail Protection will at least stop that from happening, 5 errors in 5 minutes seems a bit long but luckily you can edit this (or it appears you can).  In IIS Manager select the Application Pool in question and click Advanced Settings to the right.  You will see a window like the below picture, scroll down to Rapid Fail Protection and you can disable it or change the frequencies.
rapid

It let me change it so I am assuming it will keep those settings, I have not personally tested this yet.  One last note, I would only disable this setting or really mess with it at all if its for a development/test server where you know you will be breaking things enough to cause this to go off.
 
 
I have resolved - Automatically app pool stop.
Labels:

Comments

Post a Comment

Popular posts from this blog

IPv4 header to requests when a client is using IPv6

  What is Pseudo IPv4? As a stopgap to accelerate the adoption of IPv6, Cloudflare offers Pseudo IPv4 which supports IPv6 addresses in legacy applications expecting IPv4 addresses. The goal is to provide a nearly unique IPv4 address for each IPv6 address, using Class E IPv4 address space, which is designated as experimental and would not normally see traffic. To learn more see  here . Options Add header:  Add additional Cf-Pseudo-IPv4 header only Overwrite headers:  Overwrite the existing Cf-Connecting-IP and X-Forwarded-For headers with a pseudo IPv4 address Cloudflare
Post a Comment
Read more

IIS 7 Tip # 5 Run a command when Rapid Fail Protection is triggered

Rapid-Fail Protection disables application pools if they crash multiple times within in a specified time period. This prevents the failing application pool from getting into a continuous loop of crashing and restarting. This protects other application pools running on the server as repeated failures can consume lot of system resources. When rapid-fail protection kicks in it stops the application pool that is repeatedly crashing and your clients will start getting a 503 – Service Unavailable error. An administrator will have to manually enable the application pool again. You also have to option to configure an executable to run when ever rapid-fail protection is triggered. For example below I have configured the application pool to restart the IIS service using iisreset.exe … the /rebootonerror will reboot the whole server if iisreset.exe for some reason fails to restart the services. Refer http://blogs.msdn.com/b/vijaysk/archive/2009/03/13/iis-7-tip-5-run-a-command-when-rapid-f...
1 comment
Read more

SSL Certificates without Non-FQDNs- Fully Qualified Domain Name

Over the years, publicly-trusted CAs have issued SSL certificates with domain names of different types. The most common is the Fully Qualified Domain Name (FQDN). This is a certificate that has been issued with a name registered with an entity that manages a top-level domain (TLD), for example server1.domain.com. The differentiating characteristic about an FQDN is that it is unique . There is one controller of domain.com and that controller determines who can have any name under that root, such as server1.domain.com. Along the way, public CAs also issued certificates with non-FQDNs, such as: Server host name only, for example: server1 Server name with non-managed TLD, for example: server1.domain.local (In this example, local is not a TLD per ICANN.) Reserved IP addresses (In this case, the IP address cannot be registered, see IPv4 and IPv6.) Many SSL certificates have been issued that contain non-unique domain identifiers. Correspondingly, there are many security risks w...
Post a Comment
Read more