Why can WebSphere MQ Series not be started on remaining node after a node crash?
Issue
We are using IBM Websphere MQ Series tool for customer critical file transfer. WebSphere MQ Series related processes are handle by the Red Hat Cluster Suite. WebSphere MQ is related on GFS2 shared storage. We faced the following issue
- When one node crash the MQ Series Queue manager service will not be started on the remaining cluster node, as it was identified to be running already.
- Using the MQ series related command (for debugging), we observed that the Queue manager is not really running and it is in stopped state.
Environment
- Red Hat Enterprise Linux 5
- Red Hat Cluster Suite
- GFS2
- WebSphere MQ
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.