|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
ClusterSender Auto creation |
« View previous topic :: View next topic » |
Author |
Message
|
lecmns |
Posted: Thu Jul 01, 2004 10:26 pm Post subject: ClusterSender Auto creation |
|
|
Apprentice
Joined: 26 Dec 2001 Posts: 36
|
Hi
We have some weird issues with the CLUSTER concepts / implementation.
To begin with..
we have created a QueueManager "CLServer1"
and altered it to be the full repository of cluster "CLS"
we created a clusterReceiver on "CLServer1"
now, we created a second QueueManager "CLServer2"
and made it as another full repository QueueManager in the same cluster "CLS"
we created a clusterReceiver and a clusterSender [pointing to CLServer1] on "CLServer2"
Now, we could see a ClusterSender automatically generated on "CLServer1" pointed towards "CLServer2".
We created a ClusterQueue "CLSQTWO" on "CLServer2".
Now, we could see the clusterQueue "CLSQTWO" from "CLServer1". We could also put messages from "CLServer1" to "CLSQTWO" in "CLServer2"
No confusion till this point...
We created another full repository QueueManager "CLServer3" to be a part of the cluster "CLS".
We created a ClusterReceiver on "CLServer3"
Now, we DID NOT create a ClusterSender on "CLServer3" to any of the existing full repository QueueManagers.
However we created a clusterSender from "CLServer1" to "CLsever3".
Now we could see the cluster Queue "CLSQTWO" from "CLServer3" and also could put messges into that from "CLServer3".
We did see clusterSenders created automatically from "CLServer3" towards "CLServer1" and "CLServer2".
Now, we created a clusterQueue "CLSQTHREE" in "CLServer3". But this clusterQueue WAS NOT VISIBLE from "CLServer1" or "CLServer2".
Now, that's confusing!
So, in short..
In the first scenario..
without a clusterSender channel created on "CLServer1", we could see the clusterQueue hosted on CLServer2 from CLServer1
In the second scenario, we DID NOT CREATE a clusterSendeer channel on "CLServer3", but WE DID create manually a clusterSender channel from "CLServer1" towards "CLServer3" so that the cluster information will be replicated to CLServer3 as well from CLServer1[that's happening because we found clusterSender automatically created from CLServer3 towards CLServer1 as well as towards CLServer2]
BUT.. the clusterQueue [CLSQTHREE] created in CLServer3 WAS NOT visible in CLServer1 as well as in CLServer2.
So, the question is..
for a cluster to work properly or in short to add a new full repository QueueManager to a cluster with multiple full repository QueueManagers, is it mandatory to create clusterSender channel from the new full repository QueueManager side to any of the existing full repository QueueManager?
Please provide us with some pointers on related issues if any. If you are feeling that we are going wrong somewhere, please clarify..
thanks in advance |
|
Back to top |
|
 |
EddieA |
Posted: Fri Jul 02, 2004 7:52 am Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
Quote: |
is it mandatory to create clusterSender channel from the new full repository QueueManager side to any of the existing full repository QueueManager |
Yes. Every full repository must be connectected to every other full repository with manually defined channels.
There is a reference to this in the cluster manual, but it's not obvious.
BTW. There's no real reason to ever have more than 2 full repositories in a cluster.
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
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
|
|
|
|