IBM Support

Best practices for integrating MuleSoft IBM MQ connectors with IBM Sterling Order Management MQ servers

General Page

When integrating MuleSoft IBM MQ connectors with IBM Sterling Order Management MQ servers, apply the following best practices to ensure the MuleSoft client is able to successfully reconnect in the event the TCP connection is terminated.

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:

  1. MuleSoft MQ Client logs showing the failures and attempted reconnects per the re-connection strategy.
  2. TCP packet captures between the client and the destination server.
    • Port: 15443
    • Hostname: <tenant_code>-<env>-<envno>-mq.oms.supply-chain.ibm.com 
For more details, refer to:
https://www.ibm.com/docs/en/order-management?topic=mq-external-integrations



 

[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"ARM Category":[{"code":"a8m0z000000cy06AAA","label":"Services and MQ"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"SaaS"}]

Document Information

Modified date:
17 September 2024

UID

ibm17168677