FIX: Incoming client may not be processed when the worker process for an application pool is recycled in IIS 6.0 (908739)

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

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.