My contemplations and diurnal novelties are publicized here


Goto

Run –> inetmgr –> enter –> click on App Pool  -> right-click on App –> set Application Pool Defaults –> just change everything with (seconds) to 600 instead of 90.


When you are debugging, IIS will not service any other requests until you are done stepping through your code. That includes the “ping” request that IIS sends to itself. Since IIS doesn’t hear back from itself, it decides to shut itself down, which promptly terminates your debugging.

The solution is to increase the Ping Maximum Response Time in the application pool settings from its default value of 90 seconds. Set it to something high enough that will give you enough time to debug your code (like maybe 600 seconds).

Microsoft has a long-winded write-up here, or you can just look at the pretty picture.


Edit: Others have suggested setting “Ping Enabled” to false. There are several reasons why I prefer to keep it in place, just with a larger interval, but the most important is that you will (most likely) have worker processing pinging enabled on production, and you should strive to develop and debug under a configuration that is as close to production as possible. If you do NOT have ping enabled on production, then by all means disable it locally as well.

Copied from:-

http://stackoverflow.com/questions/1421578/why-does-debugging-keep-timing-out-in-iis7

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: