Article ID: 2459833 - View products that this article applies to.
This article describes a software update that enables support for the IBM WebSphere MQ backout queue feature in the WCF Channel for WebSphere MQ feature. The WCF Channel for WebSphere MQ feature is part of Microsoft Host Integration Server 2010.
The backout queue feature that is included with IBM WebSphere MQ is a local queue that is used to store poison messages. Poison messages are MQ messages that cannot be processed and that are repeatedly returned to the message queue. If poison messages are not deleted from the message queue, they could lead to deadlocks that may affect application performance.
The IBM WebSphere MQ queue manager keeps a record of the number of times that each message is backed out. When the number reaches a configured backout threshold, the message can be moved to a backout queue. MQ does not automatically move poison messages. It is the responsibility of the program to move them to a backout queue. An MQ application at the transport layer can query the backout count and decide what to do with the message. For example:
Software update informationA supported feature that changes the product's default behavior is now available from Microsoft. However, this feature is intended to change only the behavior that this article describes. Apply it only to systems that specifically require it. This feature may receive additional testing. Therefore, if your system is not severely affected by the lack of this feature, we recommend that you wait for the next Host Integration Server 2010 service pack that contains this feature.
To obtain this feature immediately, contact Microsoft Customer Support Services. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:
File informationThe English (United States) version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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.
For Microsoft Host Integration Server 2010 32-bit edition
Collapse this tableExpand this table
For Microsoft Host Integration Server 2010 64-bit edition
After you apply the update, the WCF Channel for Websphere MQ can be configured to use a backout queue feature by setting the new MoveMessageToBackoutQueue binding property to True.
Collapse this tableExpand this table
The backout queue feature is supported only on a receive (get) operation and only when transactions are enabled. Also, the backout queue cannot be used in combination with ReceiveContext.
If the MoveMessageToBackoutQueue property is set to True, and if the Transaction and SyncPoint properties are True, the following process will occur during an MQGet operation:
The following are examples that display how the relevant properties must be configured to enable the backout queue feature.
If the properties are set in the application code
WebSphereMQBinding mqbinding = new WebSphereMQBinding();
mqbinding.ConnectionType = "ExtendedClient"; // this might be Server
mqbinding.MqcdChannelName = _ChannelName;
mqbinding.MqcdTransportType = "TCP"; // this could be SNA
mqbinding.Transaction = true;
qbinding.MqgmoSyncPoint = true;
mqbinding.MoveMessageToBackoutQueue = true; // new Backout queue binding property
If the properties are set in the AppConfig file
<mqChannelBinding>See the "Issue 6: Message backouts" topic in the following document for additional details about the usage of the backout queue feature by the IBM Websphere MQ:
<binding name="TransactionalSendReceiveSampleBinding" connectionType="ExtendedClient"
mqcdTransportType="TCP" mqgmoSyncPoint="true" transaction="true">
Best Practices: WebSphere MQ shared queues and application programs
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.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.