Some customer's may face an issue while reconnecting to the MQ server after a network glitch or failover/failback activity. This issue happens when the connection pooling is enabled in the customer's environment.

=================================
Error closing destination B[] with close option MQCO_NONE, message: MQRC_CONNECTION_BROKEN Warning: backout failed: MQJE001: Completion Code '2', Reason '2009'
=================================

Common causes for this code follow.

1). A firewall has terminated the connection.
2). An IOException caused the socket to be closed.
3). An explicit action caused the socket to be closed by one end.
4). The queue manager is offline.
5). The maximum number of channels allowed by the queue manager are already open.
6). A configuration problem in the Queue Connection Factory (QCF) (If you are using Queue Connection Factory Pool).

The MQ plugin was not able to clear the stale/hung connections. You may need to restart the BW engine to recreate the connection again. This behavior is not a plugin defect as this is an MQ Java API defect.

MQRC-CONNECTION-BROKEN-Warning-backout-failed-MQJE001-Completion-Code-2-Reason-2009 Error closing destination B[] with close option MQCO_NONE, message: MQRC_CONNECTION_BROKEN Warning: backout failed: MQJE001: Completion Code '2', Reason '2009'

Business Works

Follow the steps below. 

1). Customer may need to upgrade the MQ client version on at least Fix Pack 7.5.0.6.
2). The MQ plugin version 7.6 with hotfix 1 has the fix for this issue