Home
Troubleshooting
The 'display route information' command may be useful in diagnosing workload balancing problems. For more information, see the WebSphere MQ Event Monitoring book and the WebSphere MQ Script (MQSC) Command Reference.
The following list shows symptoms and their causes:
- Symptom — A cluster sender channel is in retry state.
- Symptom — DISPLAY CLUSQMGR shows CLUSQMGR names starting SYSTEM.TEMP.
- Symptom — Applications get rc=2085 MQRC_UNKNOWN_OBJECT_NAME when trying to open a queue in the cluster.
- Symptom — Applications get rc= 2189 MQRC_CLUSTER_RESOLUTION_ERROR when trying to open a queue in the cluster.
- Symptom — Messages are not appearing on the destination queues.
- Symptom — Applications put messages to a QALIAS but they go the SYSTEM.DEAD.LETTER.QUEUE rather then the TARGQ of the alias.
- Symptom — A queue manager does not appear to have up to date information about queues and channels in the cluster.
- Symptom — No changes in the cluster are being reflected in the local queue manager.
- Symptom — DISPLAY CLUSQMGR, shows a queue manager twice.
- Symptom — RESET CLUSTER and REFRESH CLUSTER commands were issued, but the queue manager would not rejoin the cluster.
- Resolving Problems
Parent topic:
Troubleshooting
qc13090_
Home