Assume that you have a WCF receive location in Microsoft BizTalk Server 2010, BizTalk Server 2013 R2, or BizTalk Server 2013. You disable the receive location, and a client application continues to make calls to this disabled receive location. In this situation, the thread count and memory consumption of the WCF host grow. This growth keeps continuing while the receive location is disabled.
This issue occurs because the time-out value of WCF does not synchronize with the receive time-out when there is no data to poll. Additionally, WCF opens a new channel and waits for messages on the new channel, and this may cause a memory leak.
Cumulative update information
This issue was first fixed in the following cumulative update of BizTalk Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For information about the service packs and cumulative update list for BizTalk Server, see KB 2555976: Service pack and cumulative update list for BizTalk Server.
For more information about BizTalk Server hotfixes, see KB 2003907: Information about BizTalk hotfixes and Service Pack support.