This article was previously published under Q321792
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
If the ASP.NET worker process has been idle for the time that is specified for the responseDeadlockInterval configuration setting in the Machine.config file, the ASP.NET worker process (Aspnet_wp.exe) is recycled unexpectedly.
The following event is logged in the Application event log:
Event Type: ErrorEvent Source: ASP.NET 1.0.3705.0Event Category: NoneEvent ID: 1003Date: 4/24/2002Time: 6:18:23 PMUser: N/AComputer: <ComputerName>Description:aspnet_wp.exe (PID: <xxx>) was recycled because it was suspected to be in adeadlocked state. It did not send any responses for pending requests in thelast 180 seconds.
NOTE: This event is expected if you experience a deadlock scenario. Before you apply the hotfix that is listed in the "Resolution" section, you must rule out a deadlock scenario. If your problem is caused by a deadlock, you do not need this hotfix.
To rule out a deadlock scenario, use one of the following methods:
Open Performance Monitor, and then add the Requests Executing counter for the ASP.NET Application object. If the number of requests that are executing is greater than zero at the time of the recycle, you are experiencing a deadlock.
For more information about Performance Monitor, see the Microsoft Windows Help documentation.
Attach a native debugger to the Aspnet_wp.exe process, and then dump out the threads. If any of the threads are currently processing a request, you are experiencing a deadlock. In this case, examine the thread that is processing a request to determine what is causing the request to stop responding (hang).
To resolve this problem, obtain the latest service pack for Microsoft .NET Framework. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
318836 INFO: How to Obtain the Latest .NET Framework Service Pack
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name -------------------------------------------------------------- 21-Apr-2002 12:15 1.0.3705.258 192,512 Aspnet_isapi.dll 21-Apr-2002 12:10 19,332 Aspnet_perf.ini 21-Apr-2002 12:15 1.0.3705.258 24,576 Aspnet_regiis.exe 21-Apr-2002 12:15 1.0.3705.258 28,672 Aspnet_wp.exe 05-Apr-2002 12:07 8,709 Smartnav.js 05-Apr-2002 12:07 7,003 Smartnavie5.js 22-Apr-2002 00:39 1.0.3705.258 1,183,744 System_web.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft .NET Framework Service Pack 2 (SP2).
Under certain scenarios, the request processing logic may not be synchronized. This can cause the deadlock detection mechanism to engage if no requests have been received for the time that is specified in the responseDeadlockInterval attribute in the <processModel> element of your Machine.config file.
NOTE: You can frequently reproduce this problem when you run under Secure Sockets Layer (SSL).