| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Cluster doesn't work now |
« View previous topic :: View next topic » |
| Author |
Message
|
| mehedi |
 Posted: Fri Dec 12, 2003 2:05 pm Post subject: Cluster doesn't work now |
 |
|
Centurion
Joined: 11 Nov 2001
Posts: 102
Location: PSTech
|
Here is what happened.
The full repository QM ABCD of a cluster WRK was recreated.
Everthing worked fine.Then one day
Applicaitons connecting to cluster queue on ABCD through QM EFGH started failing.
The error log on ABCD shows repository messages from EFGH were getting through
----- amqrrmfa.c : 34152 ------------------------------------------------------
12/12/03 16:09:59
AMQ9412: Repository command received for 'ABCD_2001-11-27_15.42.20'.
EXPLANATION:
The repository manager received a command intended for some other queue
manager, whose identifier is 'ABCD_2001-11-27_15.42.20'. The command was sent
by the queue manager with identifier 'EFGH_2003-09-09_17.33.11'.
ACTION:
Check the channel and cluster definitions of the sending queue manager.
-------------------------------------------
The Queue Manager id for ABCD ('ABCD_2001-11-27_15.42.20') has an earlier timestamp.Not the timestamp from which it was created last.
Removed (suspend cluster,stop,delete cluster channels) EFGH from cluster and added(recreate clussender and cluster receiver channels) EFGH back to cluster.
Still it doesnt work now.Any suggestions.
_________________
Thanks
Mehedi Hashir
mhashir@hotmail.com |
|
| Back to top |
|
 |
| mehedi |
| Posted: Tue Dec 16, 2003 12:15 pm Post subject: How to's |
|
|
Centurion
Joined: 11 Nov 2001
Posts: 102
Location: PSTech
|
Since the QMID is never modified and it is very unlikely it got
overwritten by accident, at 5.3, RESET against the specific QMID is
possible so it is the first option that should be used here, instead of clearing
the queues.
.
If this fails, then please try the steps below;
Once it has been established that the problem comes from an incorrect
deletion of a queue manager, the following procedure can be used: (the
queue managers have the self-explanatory names PARTIAL and FULL and are
part of the cluster 'CLUSTER')
#1 - endmqm -i 'PARTIAL'
#2 - on FULL: reset cluster (CLUSTER) QMNAME(PARTIAL)
ACTION(FORCEREMOVE)
***** Wait to ensure the RESET has completed *****
#3 - endmqm -i 'FULL'
#4 - dltmqm 'PARTIAL'
#5 - crtmqm 'PARTIAL'
#6 - strmqm 'PARTIAL'
#7 - redefine cluster channel definitions.
#8 - strmqm 'FULL'
#9 - refresh cluster CLUSTER(CLUSTER) on 'FULL'
You may skip steps 4&5 can initially and see how it goes. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
