| Author |
Message
|
| senMQ |
 Posted: Sat Jan 26, 2008 10:40 am Post subject: Queue manager went out of cluster |
 |
|
Acolyte
Joined: 14 Aug 2006
Posts: 66
Location: Palo Alto, CA
|
We have prod cluster with about 30 queue managers. One of the queue managers went out of the cluster this morning. There are no specific changes made to this queue manager recently (with in the past 3 months)
A little while later, the second queue manager on the same server went out of the cluster.
Once we refreshed the cluster from these queue managers, it came back in to the cluster and messages started flowing normally.
The same thing happened about three months back on this queue manager about 3 months back. I opened a PMR with IBM for this issue. They were not able to give us an answer.
Has anyone seen such behaviour in the past ...
Any idea how this could happen? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sat Jan 26, 2008 12:02 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Define qmgr went out of the cluster ??
Were the cluster channels running, stopped or in retry mode??
Was the qmgr suspended from the cluster??
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| senMQ |
| Posted: Sat Jan 26, 2008 12:50 pm Post subject: |
|
|
Acolyte
Joined: 14 Aug 2006
Posts: 66
Location: Palo Alto, CA
|
Messages were not going in to any of the clustered queues on that queue manager. I got 2085 error when I try to put a message manually(using amqsput)
I couldn't find this queue manager's entry when I ran the dis clusqmgr(*) command on the full repository queue manager. The queue manager wasnt suspened from the cluster
The channels were not running |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jan 26, 2008 10:12 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
First order of business in a cluster:
a) make sure the cluster receiver has the right cluster name in it and is accessible from any qmgr in the cluster
b) make sure the cluster sender has the right cluster name in it and is running to a Full Repository
c) make sure the Full repository has a running channel to your PR.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Nigelg |
| Posted: Sun Jan 27, 2008 10:29 pm Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Some unknown person on your system with mqm authority issued runmqsc commands to cause the qmgr to leave the cluster.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Jan 28, 2008 10:31 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jan 28, 2008 10:41 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Yes, this is my line of thinking. That something has caused the repository to stop populating new data - either because the (iSeries equivalent of) amqrrmfa is not running, or because something is wrong with SYSTEM.CLUSTER.REPOSITORY.QUEUE.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
