New JMSReceiver Component created is Failing With Timeout And MQ Connectivity Errors ('MQRC_HOST_NOT_AVAILABLE')
(Doc ID 2712693.1)
Last updated on JUNE 05, 2024
Applies to:
Siebel CRM - Version 20.1 and laterInformation in this document applies to any platform.
Symptoms
On a Test / UAT environment, a custom JMS Receiver component was created but it was not working fine - as errors reported in JMS logs:
[SIEBEL ERROR] Thread[http-nio-8081-exec-5,5,main] [8:11:29.836 PM Wed Sep 9: ] Receive failed.
[SIEBEL ERROR] Thread[http-nio-8081-exec-5,5,main] [8:11:29.836 PM Wed Sep 9: ] Exception during Receive:
com.ibm.msg.client.jms.DetailedIllegalStateException: JMSWMQ0018: Failed to connect to queue manager 'QMCERIN1' with connection mode 'Client' and host name '[hostname].[domain](1417)'.
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.
...
Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2538' ('MQRC_HOST_NOT_AVAILABLE').
at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:203)
... 72 more
The issue could be reproduced with the following steps:
1. Clone an existing JMSReceiver component;
2. Check the Siebel details and parameters setup / change them as needed;
3. Start the component and check if it able to process requests - see the errors reported in JMS logs.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |