Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: The WCF-Custom adapter does not close the connection to a WCF-based service in BizTalk Server if a WCF-based typed fault occurs

FIX: The WCF-Custom adapter does not close the connection to a WCF-based service in BizTalk Server if a WCF-based typed fault occurs

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You create a solicit-response send port in Microsoft BizTalk Server 2009 or in Microsoft BizTalk Server 2010. This port uses the Windows Communication Foundation (WCF)-Custom adapter to send and receive messages from a WCF-based service.
  • The Propagate fault message check box for the send port is not selected.
  • A WCF-based typed fault occurs in the WCF-based service.
In this scenario, the WCF-Custom adapter incorrectly maintains the connection to the WCF-based service. Additionally, the WCF-based service stops responding when the throttling values of the service reach either the value of the MaxConcurrentInstances or MaxConcurrentSessions property.

↑ Back to the top

Cause

This issue occurs because the WCF-Custom adapter incorrectly closes the channel instead of the connection.

↑ Back to the top

Resolution

Cumulative update information


BizTalk Server 2010


For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2497789 Cumulative update package 1 for BizTalk 2010

For BizTalk Server 2009, the hotfix that resolves this issue is included in Cumulative Update 1 for BizTalk Server 2009.

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2429050 Cumulative update package 1 for BizTalk Server 2009


↑ Back to the top

Workaround

To work around this issue, use one of the following methods:

  • Restart Internet Information Services (IIS) from the computer that hosts the WCF-based service after the service stops responding.
    Notes
    • To restart IIS 6.0, open IIS Manager, right-click the computer name, point to All Tasks, click Restart IIS, and then click OK.
    • To restart IIS 7.0 or IIS 7.5, open IIS Manager, select the computer name, and then click Restart on the Actions panel.
  • Set the MaxConcurrentSessions and MaxConcurrentInstances properties for the service to a larger value.

↑ Back to the top

Status

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

↑ Back to the top

More Information

If this issue occurs in Microsoft BizTalk Server 2006 R2, try one of the methods that are documented in the "Workaround" section.

For more information about WCF-Custom transport properties, visit the following Microsoft Developer Network (MSDN) website:
General information about WCF-Custom transport properties

For more information about how to optimize the performance of the BizTalk Server WCF-based adapter, visit the following MSDN website:
How to optimize the performance of the BizTalk Server WCF-based adapter
For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

2003907 Information about BizTalk Server hotfixes


For more information about how to handle the typed fault contracts in orchestrations, visit the following MSDN website:
How to handle the typed fault contracts in orchestrations

↑ Back to the top

Keywords: kbqfe, kbfix, kbexpertiseadvanced, kbsurveynew, kbbtsadapters, kbbiztalk2009presp1fix, kb

↑ Back to the top

Article Info
Article ID : 2431074
Revision : 2
Created on : 9/10/2018
Published on : 9/11/2018
Exists online : False
Views : 438