Troubleshooting
Problem
IBM MQ JMS protocol no longer pulls the event from the Queue due to configuration problems
Resolving The Problem
Following is the error that we get upon pulling events from the Queue.
MQJMS error message: JMSCMQ0001: WebSphere IBM MQ call failed with comp code '2' ('MQCC_FAILED') reason '2538' ('MQRC_HOST_NOT_AVAILABLE').
MQJMS error message: JMSCMQ0001: WebSphere IBM MQ call failed with comp code '2' ('MQCC_FAILED') reason '2538' ('MQRC_HOST_NOT_AVAILABLE').
The error message from IBM MQ was generic and had no straightforward suggestions to take action.
Few things to check when you get these error messages.
Check the configuration. There might be missing permission caused by installing a fix pack on the IBM MQ server.
There might be a problem with permissions setup in the message Channel Agent in IBM MQ terminology.
The agent might have GET (read) permission. Still, another authorization (BROWSE) was not delegated, and because of that, the service account might not be able to fetch messages [after a fix pack installation on the IBM MQ server].
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"ARM Category":[{"code":"a8m0z000000cwt3AAA","label":"QRadar Apps"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
24 January 2023
UID
ibm16842523