| Author |
Message
|
| Vitor |
 Posted: Fri Aug 10, 2012 9:14 am Post subject: Re: alias queue from a qm shared in two clusters |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vimmy wrote: |
| I have a secnario where we had to overlap clusters. |
Why?
| vimmy wrote: |
| Please advise me how to go about solving this. |
Read the advice given above, i.e. don't overlap clusters. What you're describing here is what I described as one of classic problems with overlapping clusters towards the top of this thread.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| vimmy |
| Posted: Fri Aug 10, 2012 10:00 am Post subject: |
|
|
Novice
Joined: 29 Jan 2011
Posts: 15
|
| Well,...We had to cluster the WMS queue manager as well and we are implementing queue processors where in the same WMS mainframes has code to service multiple environments. Looks like that alias queues and corresponding target queues withing the same cluster does not stop messages spaying over to other clusters. Is there a way I can control this/ |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Aug 10, 2012 10:30 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
WMQ uses exactly the {queue manager, queue} name or {topic} when it is routing messages.
You need to control what names your applications fill into those pieces.
You then need to control how those names are resolved across your MQ network.
That is how you fix this problem.
As has been said several times in the rest of this thread, DO NOT OVERLAP CLUSTERS unless you want them to overlap completely. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Aug 10, 2012 11:03 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
The target queues need to be clustered in only the cluster whose cluster channels you want to use.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| vimmy |
| Posted: Fri Aug 10, 2012 11:47 am Post subject: |
|
|
Novice
Joined: 29 Jan 2011
Posts: 15
|
| Yes.. the target and the alias queues are shared in the same cluster.. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Aug 10, 2012 1:52 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
So its working as designed.
Your target queues are clustered in "Cluster1" and MQ is load balancing to them.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mattfarney |
| Posted: Sat Aug 11, 2012 1:44 pm Post subject: |
|
|
Disciple
Joined: 17 Jan 2006
Posts: 167
Location: Ohio
|
The only use I have personally found for overlapping clusters is when the clusters are controlled by different people/organizations/etc.
-mf |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sat Aug 11, 2012 3:36 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I've used them to provide different classes of delivery. Small non persistent time sensitive messages were sent in the cluster that had channel parameters optimized for them, large honkin' non-time sensitive messages from batch jobs were sent in the cluster down channels optimized for them.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Aug 11, 2012 4:23 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I've used them to isolate application-specific clusters that need access to a common application or hub.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
