Microsoft KB Archive/841557

= The ASP.NET worker process restarts before the timeout setting has lapsed =

Article ID: 841557

Article Last Modified on 7/7/2004

-

APPLIES TO


 * Microsoft ASP.NET 1.1
 * Microsoft ASP.NET 1.0

-



SYMPTOMS
The Microsoft ASP.NET worker process Aspnet_wp.exe restarts or is recycled before the timeout setting that is specified in the ScriptTimeout property, the Session.Timeout attribute, the executionTimeout property, or another setting, has lapsed. The following error message is logged in the application event log:

Event Type: Error

Event Source: ASP.NET 1.0.3705.0

Event Category: None

Event ID: 1003

Date: 4/24/2002

Time: 6:18:23 PM

User: N/A

Computer: 

Description: aspnet_wp.exe (PID: ) was recycled because it was suspected to be in a deadlocked state. It did not send any responses for pending requests in the last 180 seconds.



CAUSE
This problem occurs when the ASP.NET worker process has been idle for the duration that is specified in the responseDeadlockInterval configuration setting in the Machine.config file. This behavior causes the deadlock detection mechanism to restart the worker process. Then, the deadlock detection mechanism writes an error message in the application event log that indicates that the restart occurred because of a suspected deadlock state. For example, a slow write to the client may take longer than the value of the responseDeadlockInterval configuration setting in the Machine.config file.



RESOLUTION
In the  section of the Machine.config file, increase the responseDeadlockInterval configuration setting. Set a maximum value that is at least the same as your longest application-level timeout setting. You may also set the responseDeadlockInterval configuration setting to Infinite. This configuration setting affects all ASP.NET applications that run on the server. The Machine.config file is typically located in the C:\ \Microsoft.NET\Framework\ \CONFIG folder.

Note  is the version number of the Microsoft .NET Framework that you installed on your server. is your Microsoft Windows folder. Typically, your Microsoft Windows folder is C:\Windows\.

To increase the responseDeadlockInterval configuration setting, follow these steps:
 * 1) Click Start, click Run, type notepad, and then click OK.
 * 2) In Notepad, click File, click Open, locate the C:\ \Microsoft.NET\Framework\ \CONFIG folder, click All files in the Files of type list, click Machine.config in the file list, and then click OK.
 * 3) Locate the responseDeadlockInterval configuration setting in the Machine.config file, and then change the value to the one that you want.
 * 4) Save the Machine.config file, and then close Notepad.

The following code is the  section of the Machine.config file where the responseDeadlockInterval configuration setting appears: <processModel enable=&quot;true|false&quot; timeout=&quot;hrs:mins:secs|Infinite&quot; idleTimeout=&quot;hrs:mins:secs|Infinite&quot; shutdownTimeout=&quot;hrs:mins:secs|Infinite&quot; requestLimit=&quot;hrs:mins:secs|Infinite&quot; requestQueueLimit=&quot;num|Infinite&quot; restartQueueLimit=&quot;num|Infinite&quot; memoryLimit=&quot;percent&quot; cpuMask=&quot;num&quot; webGarden=&quot;true|false&quot; userName=&quot;username&quot; password=&quot;password&quot; logLevel=&quot;All|None|Errors&quot; clientConnectedCheck=&quot;hrs:mins:secs|Infinite&quot; responseDeadlockInterval=&quot;hrs:mins:secs|Infinite&quot; responseRestartDeadlockInterval=&quot;hrs:mins:secs|Infinite&quot; comAuthenticationLevel=&quot;Default|None|Connect|Call| Pkt|PktIntegrity|PktPrivacy&quot; comImpersonationLevel=&quot;Default|Anonymous|Identify| Impersonate|Delegate&quot; maxWorkerThreads=&quot;num&quot; maxIoThreads=&quot;num&quot;/>

Keywords: kbprb KB841557

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.