Consider the following scenario:
You have a Microsoft BizTalk Server host instance that has one receive port.
The receive port has multiple receive locations that use the Microsoft BizTalk Adapter for DB2.
The receive locations poll an IBM DB2 system.
You disable one of the receive locations in a Microsoft Host Integration Server 2010 environment.
In this scenario, the active receive locations stop polling the IBM DB2 system.
When the receive location that you disabled is re-enabled, that receive location resumes polling the IBM DB2 system. However, the other receive locations do not resume polling.
When the BizTalk Server application is restarted, all the receive locations resume polling.
This problem occurs because the BizTalk Adapter for DB2 does not re-create internal timers when changes are made to any BizTalk Adapter for DB2 properties or to the receive locations. This failure to re-create internal timers results in the following behavior:
The BizTalk Adapter for DB2 stops polling across all receive locations when one receive location is stopped.
Changes that you make to the BizTalk Adapter for DB2 are not made dynamically. For example, this is true when the DB2 stored procedure that is being called is changed.
Cumulative update information
Microsoft Host Integration Server 2010
The fix that resolves this problem is included in cumulative update package 8 for Host Integration Server 2010. For more information about how to obtain the cumulative update package, see Cumulative update package 8 for Host Integration Server 2010.
Microsoft Host Integration Server 2009
The fix that resolves this problem is included in Cumulative Update 6 for Host Integration Server 2009.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
After you apply this update, any changes that are made to the BizTalk Adapter for DB2 are made dynamically. Additionally, receive locations can be stopped and started without affecting the other receive locations.
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.