| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MY MQ CLUSTER PROBLEM |
« View previous topic :: View next topic » |
| Author |
Message
|
| leoChina |
 Posted: Thu Sep 04, 2008 7:48 pm Post subject: MY MQ CLUSTER PROBLEM |
 |
|
Novice
Joined: 04 Sep 2008
Posts: 14
|
hi,everybody
when i created a mq cluster,i found a problem that the second mqm could not display correctly in the cluster view.it displays as a system temp mqm,just like the mqm had not been added into the cluster.but in this mqm channel ,i can find out the cluster channel..
what happens to my mq?everybody's answer is welcome.thanks all.
-------------
MSN:geningcao@hotmail.com |
|
| Back to top |
|
 |
| AkankshA |
| Posted: Thu Sep 04, 2008 10:17 pm Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
check out the clustering manual.. troubleshooting section
your cluster channesl are not in ruunning status
_________________
Cheers |
|
| Back to top |
|
|
| jhidalgo |
| Posted: Fri Sep 05, 2008 9:04 am Post subject: |
|
|
Disciple
Joined: 26 Mar 2008
Posts: 161
|
Leo, you can check the dynamic channels(not shown in the channels list) with the folloing command:
display chstatus(*)
Also check if the system.cluster.transmit.queue is empty, if not see the destinations that it can not contact.
Make sure your partial repositories point to BOTH of your full repositories, also make sure your partial repositories have the cluster receiver channel and the listener running, and also when you want to delete and recreate a qmgr that was part of the cluster you have to:
(all this with the cluster channels running)
1. clear the repos attribute if it is a repository
2. suspend the qmgr from the cluster
3. clear the cluster attribute from the cluster receiver
4. stop and then delete the cluster receiver
5. issue the refresh cluster information
6. stop and then delete the cluster sender |
|
| Back to top |
|
|
| leoChina |
| Posted: Mon Sep 08, 2008 7:17 am Post subject: |
|
|
Novice
Joined: 04 Sep 2008
Posts: 14
|
oh,i am glad to get your reply,AkankshA and jhidalgo!
with your advice,i found this problem appear when the channel can not be started.
and in my case,i set the channel with the hosts name instead of IP.The cluster seems to mistake for the mqm.after changing,i found everything in right status.
thank you again,and i will expect your opinion.
-------------
MSN:geningcao@hotmail.com |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Sep 08, 2008 2:35 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| leoChina wrote: |
oh,i am glad to get your reply,AkankshA and jhidalgo!
with your advice,i found this problem appear when the channel can not be started.
and in my case,i set the channel with the hosts name instead of IP.The cluster seems to mistake for the mqm.after changing,i found everything in right status.
thank you again,and i will expect your opinion.
-------------
MSN:geningcao@hotmail.com |
Usually clustering works much better with the host name instead of the IP. The reason is that in well behaved networks the host names tend to be unique and accessible from all cluster members whereas the IP might have to go through NAT traversal mapping and other stuff.
Enjoy 
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
