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

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.

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

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:

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:

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.

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

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:

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

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