IBM MQ Connector is not able to connect to a secondary queue manager host in the name list of a multi-instance queue manager

SYMPTOM

Mule-IbmMqConnector-foreverreconnection-logs
|transactionId=|application=|auditEvent=|auditObject=|muleFlow=|muleMessageId=|payload=|businessKeyCd
=| - [[MuleRuntime].io.136: [uw-ods-publishing-accord-async-
api].io@org.mule.runtime.module.extension.internal.runtime.source.ExtensionMessageSource.lambda$null$
9:305 @681d06ba] org.mule.jms.commons.internal.connection.provider.JmsConnectionProvider:
com.ibm.msg.client.jms.DetailedIllegalStateException: JMSWMQ0018: Failed to connect to queue manager
'DTSMODEL' with connection mode 'Client' and host name 'primaryQMHost.yourdomain.net(1416),secondaryQMHost.yourdomain.net(1416)'.
Check the queue manager is started and if running in client mode, check there is a listener running.
Please see the linked exception for more information.
at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_222]
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2538;AMQ9204: Connection to host 'primaryQMHost.yourdomain.net(1416)' rejected. [1=com.ibm.mq.jmqi.JmqiException[CC=2;RC=2538;AMQ9204: Connection to
host 'primaryQMHost.yourdomain.net/nn.nn.nn.nn:1416' rejected.
[1=java.net.ConnectException[Connection refused (Connection refused)],3=primaryQMHost.yourdomain.net/nn.nn.nn.nn:1416,4=TCP,5=Socket.connect]],3=primaryQMHost.yourdomain.net(1416),4=,5=RemoteTCPConnection.bindAndConnectSocket]

ERROR 2022-07-29 12:16:02,228 [[MuleRuntime].uber.14: [ibmmqpubsub].uber@org.mule.runtime.module.extension.internal.runtime.source.ExtensionMessageSource.lambda$null$16:416 @34e1eced] [processor: ; event: ] org.mule.jms.commons.internal.connection.provider.JmsConnectionProvider: com.ibm.msg.client.jms.DetailedJMSSecurityException: JMSWMQ2013: The security authentication was not valid that was supplied for queue manager 'QM1' with connection mode 'Client' and host name 'ec2-nn-nn-nn-nn.us-west-1.compute.amazonaws.com(1414),localhost(1414)'.
Please check if the supplied username and password are correct on the queue manager to which you are connecting.  For further information, review the queue manager error logs and the Securing IBM MQ topic within IBM Documentation.

CAUSE

SOLUTION