ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Clustering » Cluster Problem

Post new topic  Reply to topic
 Cluster Problem « View previous topic :: View next topic » 
Author Message
reeturaj_sunny
PostPosted: Fri Aug 04, 2006 1:21 am    Post subject: Cluster Problem Reply with quote

Newbie

Joined: 26 Jun 2006
Posts: 9
Location: Mumbai,India

Hi All,

I have created a cluster of 3 queue managers(QM1,QM2,QM3).
All the queue manages are on the local Windows machine.

QM1 and QM2 hold the repository.

I connected QM3 to the QM1 repository queue manager.

When I created a local queue in QM3,that was visible to QM1 and QM2 also.

When I created a local queue in QM1,that was visible to QM2 and QM3 also.

But when I created a local queue in QM2,that was visible to QM1 but not to QM3.

Later when I changed QM3 to repository queue manager,then the queue was visible.


Why is it so?

Pls help...................
Back to top
View user's profile Send private message Yahoo Messenger
Vitor
PostPosted: Fri Aug 04, 2006 1:30 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Queue managers that are not full repositories (FR) only contain details of queues that they think they need. Rules for partial repository (PR) updating & clean up are in the manual. Hence if you add a queue to a PR both of the FR get details because they hold everything. You add a queue to a FR, the PR will only take the details on first use (assuming throughout the queues are shared in the cluster of course!)

If you repeat the seqeunce, leaving QM3 as a PR, connect to it & open the clustered queue you'll then see the details on QM3 because it's been used & QM3 will have obtained the details it need to use it.

Functioning as designed
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Clustering » Cluster Problem
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.