General Page
When unexpected TCP terminations occur, a '2009/MQRC_CONNECTION_BROKEN' error would be observed.
To recover from TCP connection errors, use MuleSoft's Forever (reconnect-forever) strategy with a retry interval greater than the MQ Client TCP connection Timeout.
The following property can be set on the MQ Client to override the default timeout (i.e. 120 seconds) to a shorter interval.
-Dcom.ibm.mq.cfg.TCP.Connect_Timeout=30
For example, when using a 30 second Connect_Timeout, set the MuleSoft reconnect interval to 45 seconds.
Note: It is expected behavior to see some TCP connection failures during maintenance events when MQ traffic is switched within an HA pair (i.e. from active to passive). However, if very frequent 2009/MQRC_CONNECTION_BROKEN errors are observed, please create a case with IBM Support and provide the following diagnostics:
- MuleSoft MQ Client logs showing the failures and attempted reconnects per the re-connection strategy.
- TCP packet captures between the client and the destination server.
- Port: 15443
- Hostname: <tenant_code>-<env>-<envno>-mq.oms.supply-chain.ibm.com
https://www.ibm.com/docs/en/order-management?topic=mq-external-integrations
Was this topic helpful?
Document Information
Modified date:
17 September 2024
UID
ibm17168677