You may notice that a Web application exhibits the
- Long running, CPU intensive operations block other requests
from executing. This behavior causes requests to queue.
- Requests appear to be "stuck" in the request queue.
Requests that run on I/O threads that consume 100 percent of the
available CPU capacity cause the completions on the named pipes between the
Inetinfo.exe process and the Aspnet_wp.exe process to be blocked. These completions remain blocked until CPU capacity is available.
This behavior causes incoming requests to be blocked.
To avoid these issues,
requests now run on Worker threads. This scenario frees the I/O
threads to continue to process completions. Note
This scenario is a significant change in behavior. Because of this change, you may have to
configure, test, and stress the following configuration settings:
- maxIOThreads in the <processModel> section
- maxWorkerThreads in the <processModel> section
- minFreeThreads in the <httpRuntime> section
How to obtain the hotfix
This issue is fixed in the June 2003 ASP.NET Hotfix Package 1.1. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
ASP.NET 1.1 June 2003 Hotfix Rollup Package
When you request this hotfix, you receive the hotfix rollup package.
You cannot obtain this hotfix individually. You must
apply the hotfix rollup package.
If you upgrade to the .NET Framework version 1.1
If you apply the hotfix rollup package that is described in Microsoft Knowledge Base article 821156, and then you upgrade to Microsoft ASP.NET that is included with the .NET Framework 1.1, you must apply the hotfix rollup package again.
Additionally, if you experience the issues that are mentioned in the "Symptoms" section after you upgrade to the .NET Framework 1.1, you must apply the hotfix rollup package again.Note
If you have the .NET Framework 1.1 Service Pack 1 (SP1) installed, you must create a registry key to enable this hotfix.Warning
Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Create the following registry key to enable this hotfix on the .NET Framework 1.1 SP1:
Hotfix file information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone
tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
01-May-2003 12:46 1.0.3705.419 196,608 Aspnet_isapi.dll
01-May-2003 12:46 4,169 Aspnet_perf.h
01-May-2003 12:46 20,468 Aspnet_perf.ini
01-May-2003 12:46 20,342 Aspnet_perf2.ini
01-May-2003 12:46 1.0.3705.419 24,576 Aspnet_regiis.exe
01-May-2003 12:46 1.0.3705.419 28,672 Aspnet_wp.exe
01-May-2003 12:46 1.0.3705.419 69,632 Corperfmonext.dll
01-May-2003 12:46 1.0.3705.419 303,104 Mscorjit.dll
01-May-2003 12:46 1.0.3705.419 1,953,792 Mscorlib.dll
01-May-2003 12:46 10,284 Mscorlib.ldo
01-May-2003 12:46 1.0.3705.419 2,269,184 Mscorsvr.dll
01-May-2003 12:46 1.0.3705.419 2,269,184 Mscorwks.dll
01-May-2003 12:46 15 Smartnav.htm
01-May-2003 12:46 8,728 Smartnav.js
01-May-2003 12:46 1.0.3705.419 1,191,936 System.web.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 816829 - Last Review: September 27, 2005 - Revision: 6.3
- Microsoft .NET Framework 1.0
- Microsoft ASP.NET 1.0
|kbhotfixserver kbqfe kbnetframe100presp3fix kbfix kbbug KB816829|