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

Intrusion detection system

An   intrusion detection system   ( IDS ) is a device or   software application   that monitors network or system activities for malicious activities or policy violations and produces reports to a management station.  IDS come in a variety of “flavors” and approach the goal of detecting suspicious traffic in different ways. There are network based (NIDS) and host based (HIDS) intrusion detection systems. Some systems may attempt to stop an intrusion attempt but this is neither required nor expected of a monitoring system.  Intrusion detection and prevention systems (IDPS) are primarily focused on identifying possible incidents, logging information about them, and reporting attempts. In addition, organizations use IDPSes for other purposes, such as identifying problems with security policies, documenting existing threats and deterring individuals from violating security policies.  IDPSes have become a necessary addition to the security infrastru...
Post a Comment
Read more

Amazon AWS - Cloudfront configuration

Amazon Cloudfront Dynamic Content Delivery HTTP GET and HEAD   requests are currently supported by Amazon CloudFront. Over time, we will add support for POST requests.   Our sample setup You can convert your existing blog or setup a new blog from scratch to use cloudfront. For demonstration purpose, I'm going to setup a new blog called www.contentdeliverynetworklog.com and serve the whole blog via cloudfront as follows: Blog domain name:   www.contentdeliverynetworklog.com   (CNAME to cloudfront) Blog origin domain name:   cp.contentdeliverynetworklog.com . To fetch web content from this origin web server. Static asset domain name:   s0.contentdeliverynetworklog.net   (CNAME to cloudfront). Static asset origin domain name:   origin.contentdeliverynetworklog.net . Custom origin IP address for both static/dynamic assets:   75.126.153.203 Caching ruleset for your dynamic and static assets: I am going to use a combination of Batca...
8 comments
Read more