Knowledge Base

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"

Article ID: 924638

Article Last Modified on 11/15/2007

APPLIES TO

Microsoft BizTalk Server 2006 Standard Edition
Microsoft BizTalk Server 2006 Enterprise Edition
Microsoft BizTalk Server 2006 Developer Edition

SYMPTOMS

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

CAUSE

This problem occurs because you cannot set the HTTP header KeepAlive property to false when you use the HTTP adapter to send a message.

RESOLUTION

Hotfix information

A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

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

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to 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 item in Control Panel.

File name	File version	File size	Date	Time
Microsoft.biztalk.httptransport.dll	3.5.1621.0	72,512	01-Sep-2006	18:46

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

WORKAROUND

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.

HttpWebRequest HttpWRequest = 
(HttpWebRequest)WebRequest.Create("<http://ApacheServer/WritePostedDocument.asp>");


HttpWRequest.Method = "POST";
HttpWRequest.ContentType = "application/x-www-form-urlencoded";
HttpWRequest.KeepAlive =false;
byte[] PostData = Request.BinaryRead(Request.TotalBytes);
HttpWRequest.ContentLength = PostData.Length;
Stream tempStream = HttpWRequest.GetRequestStream();
tempStream.Write(PostData,0,PostData.Length);
tempStream.Close();
HttpWebResponse HttpWResponse;
HttpWResponse = (HttpWebResponse)HttpWRequest.GetResponse();
Response.Write (HttpWResponse.StatusCode);
HttpWResponse.Close();
}

MORE INFORMATION

After you apply the hotfix that is described in this article, use one of the following methods to set the KeepAlive property:

Create a property schema to set the KeepAlive property. To do this, follow these steps:
1. Create a property schema.
2. Add a KeepAlive context property.
3. Set the namespace of the schema to the following:
  
  http://schemas.microsoft.com/BizTalk/2003/http-properties
  
  Note We do not recommend that you deploy this schema because future BizTalk Server updates may include an HTTP schema to set the KeepAlive property.

Create a custom send pipeline to set the KeepAlive property to false. In the custom send pipeline, use the following code example in the IComponent.Execute method:

public Microsoft.BizTalk.Message.Interop.IBaseMessage Execute(Microsoft.BizTalk.Component.Interop.IPipelineContext pc, Microsoft.BizTalk.Message.Interop.IBaseMessage inmsg)
        {
             inmsg.Context.Write("KeepAlive","http://schemas.microsoft.com/BizTalk/2003/http-properties", false);
            return inmsg;
        }

REFERENCES

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.

Keywords: kbbtsadapters kbbts kbbug kbfix kbpubtypekc kbhotfixserver kbqfe KB924638

Microsoft KB Archive/924638

Contents