Messages may be suspended when you use the HTTP adapter to send multiple messages to an Apache Web server, and the following error message may occur in BizTalk Server 2006: "Underlying connection was closed"
This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario. In Microsoft BizTalk Server 2006, you use the HTTP adapter to send multiple messages to a remote Apache Web server. The remote Apache Web server is configured to close the connection after each message is received.
In this scenario, one or more messages may be suspended in BizTalk Server 2006. Additionally, you may receive an error message that resembles the following:
Underlying connection was closed
This problem occurs because you cannot set the HTTP header KeepAlive property to false when you use the HTTP adapter to send a message.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
No prerequisites are required.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
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 item in Control Panel.
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To work around this problem, post the data from BizTalk Server 2006 to a custom .aspx page on the local Microsoft Internet Information Services (IIS) Web server. In the custom .aspx page, use the System.Net.HttpWebRequest class to set the KeepAlive property to false when you post the data to the Apache Web server. The following code example demonstrates how to do this.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.