Configuring Engine Deadlock Recovery

You can configure the amount of time that should elapse before the ASP Server is considered deadlocked and the engine is restarted. This functionality helps to alleviate potential problems caused if an ASP engine becomes completely deadlocked and stops servicing requests, a condition that could result from failed processes, thread contention, locked database connections, and so on. The deadlock timeout value is set to 600 seconds (10 minutes) by default.

If the deadlock timeout is set to a value lower than the script timeout, the ASP engine will restart once the time specified for the deadlock timeout has elapsed. For more information about the script timeout value, see Changing the Script Timeout Value.

The default of 600 seconds may or may not be the best setting for you. Selecting the "correct" deadlock timeout value is not an exact science and depends on your specific circumstances. Web sites that pass around large amounts of data from databases will require a different timeout value than those with pages that merely manipulate a few user-specified strings.

Be careful about setting the timeout value too high. A deadlock condition exists until the deadlock timeout has elapsed and the ASP Server is restarted, so your Web site could potentially be down for the length of time specified for the deadlock timeout.

Open the Administration Console (see Accessing the Administration Console).

On the ASP Server tab of the Server Management page, click Settings.

The Server Settings page displays.

In the Deadlock timeout box, specify the number of seconds that should elapse before the ASP Server is considered deadlocked and the engine is restarted.

If the deadlock timeout is set to a value lower than the script timeout, the ASP engine will restart after the time specified for the deadlock timeout has elapsed.

Click Save, and then restart the ASP Server by clicking Restart.

Note	Restarting the ASP Server resets all Session and Application variables.