IIS6 / W2003 and responseDeadlockInterval

cicorias · Post by **cicorias** » Mon Feb 16, 2004 9:00 am

The readme indicates the responseDeadlockInterval seeting in the processModel section of the machine.config should be increased if running into issues.

However, that setting is not availablein IIS6 as the processModel section is ignored.

Is there an alternate setting that you recomend?

Post by **jclausius** » Mon Feb 16, 2004 9:15 am

Within IIS' manager, check the properties on the default application pool (assuming no-one has configured Vault to use a separate pool).

The deadlock interval's equivalence is "Shutdown worker processes after being idle for (time in minutes)".

HTH

cicorias · Post by **cicorias** » Mon Feb 16, 2004 9:22 am

That setting is equivalent to idleTimeout in processModel

cicorias · Post by **cicorias** » Mon Feb 16, 2004 9:32 am

This is the message I found on newsgroups regarding this setting & IIS - it's from MSFT (at least the poster indicate was) and possibly makes sense

In the end, we'll see what happens. If it becomes a problem I can set IIS to run in IIS 5 mode which will read the machine.config/processModel section....

http://groups.google.com/groups?hl=en&l ... gbl&rnum=2

Regarding -- responseRestartDeadlockInterval and responseDeadlockInterval --
there isn't anything comparable in IIS6 because ASP.Net is using the "report
unhealthy" mechanism to get IIS6 to recycle itself.

Post by **jclausius** » Mon Feb 16, 2004 9:42 am

ok... i see. it seems iis 6 uses some sort of "ping" model to determine if the iis process is "unhealthy".

thanks for the update.

dan · Post by **dan** » Mon Feb 16, 2004 9:43 am

If you use IIS 5 isolation mode in IIS 6 and get a crypto error when Vault users log in, be sure to read this article too:

http://support.sourcegear.com/viewtopic.php?t=14