Article ID: 908739
Article Last Modified on 12/3/2007
APPLIES TO
- Microsoft Internet Information Services 6.0
SYMPTOMS
Incoming client requests may not be processed as expected when the worker process for an application pool is recycled in Microsoft Internet Information Services (IIS) 6.0.
CAUSE
This problem occurs because the client request is received after the recycle operation for the process has started but before the process handle is closed.
RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003
Hotfix information
Prerequisites
There are no prerequisites to apply this hotfix.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
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.
Windows Server 2003. Itanium Architecture
| File name | File version | File size | Date | Time |
|---|---|---|---|---|
| Http.sys | 5.2.3790.419 | 854,016 | 06-Oct-2005 | 03:12 |
Windows Server 2003 Service Pack 1, Itanium Architecture
| File name | File version | File size | Date | Time |
|---|---|---|---|---|
| Http.sys | 5.2.3790.2542 | 795,136 | 06-Oct-2005 | 03:12 |
Windows Server 2003 Service Pack 1, x64
| File name | File version | File size | Date | Time |
|---|---|---|---|---|
| Http.sys | 5.2.3790.2542 | 535,040 | 06-Oct-2005 | 03:12 |
Windows Server 2003, x86
| File name | File version | File size | Date | Time |
|---|---|---|---|---|
| Http.sys | 5.2.3790.419 | 336,896 | 05-Oct-2005 | 23:56 |
Windows Server 2003 Service Pack 1, x86
| File name | File version | File size | Date | Time |
|---|---|---|---|---|
| Http.sys | 5.2.3790.419 | 336,896 | 05-Oct-2005 | 23:56 |
WORKAROUND
To work around this problem, disable HTTP Keep-Alives. To do this, follow these steps:
Note Disabling HTTP Keep-Alives may adversely affect server performance.
- Start IIS Manager.
- Expand
ServerName.
Note ServerName represents the name of the Web server.
- Right-click the Web site that you want to modify, and then click Properties.
- On the Web Site tab, click to clear the Enable HTTP Keep-Alives check box, and then click OK.
- Quit IIS Manager.
For more information about how to use HTTP Keep-Alives, click the following article number to view the article in the Microsoft Knowledge Base:
816517 How to optimize Web server performance in Windows Server 2003
To limit the occurrence of this problem, disable application pool recycling or extend the period between occurrences of application pool recycling. To do this, follow these steps:
- Start IIS Manager.
- Expand
ServerName.
Note ServerName represents the name of the Web server.
- Right-click the Application Pool that you want to modify, and then click Properties.
- On the Recycling tab, click to clear all check boxes to disable recycling for the Application Pool or to increase the limits specified for any selected criteria to decrease the frequency of application pool recycling.
- Quit IIS Manager.
MORE INFORMATION
When a client connects to an IIS Web server, the connection is bound to a process. The client uses this connection to the process for all subsequent requests as long as the process is still in the application pool.
However, the process does not accept subsequent connections after the shutdown process is initiated. Therefore, a connection may be lost if a request is received after the shutdown procedure for the process starts but before the process is removed from the application pool list.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.
Keywords: kbbug kbfix kbqfe kbpubtypekc kbwinserv2003presp1fix kbhotfixserver kbwinserv2003sp2fix KB908739
