| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Introducing clustered qmgrs to existing infrastructure |
« View previous topic :: View next topic » |
| Author |
Message
|
| mqnomad |
 Posted: Tue Apr 20, 2010 8:50 am Post subject: Introducing clustered qmgrs to existing infrastructure |
 |
|
Acolyte
Joined: 18 Mar 2010
Posts: 53
|
THow are large MQ clustered environment handling getting a correlated reply from a clustered queue manager application where the reply can come from one of two queue managers?
his post refers to a very large multi-national organization.
As in many environments, MQ grew, staff changed, now situation is becoming stressful.
There is a single queue manager (with HA failover) - which handles a very critical role.
One thought was to make this a queue manager cluster, but there has been a resistance to go this route because when the clients need to get the reply, they only connect to the one queue manager.
It seems that they should alter the application to get the reply from the more likely queue manager first, but if no msg. is received then try to get it from the second queue manager (depending on how the cluster distribution is configured) - so, perhaps making the one box be the likely receiver of the msg about 70% of the time, so the double gets would only be done on exception.
How are these environments handling getting a correlated reply from a clustered queue manager application where the reply can come from one of two queue managers? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Apr 20, 2010 9:09 am Post subject: Re: Introducing clustered qmgrs to existing infrastructure |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqnomad wrote: |
| How are these environments handling getting a correlated reply from a clustered queue manager application where the reply can come from one of two queue managers? |
Because the reply will (if everything's done right) be addressed back to the requesting queue manager where the application is waiting. Remember that even in a cluster an application is only connected to a single queue manager.
| mqnomad wrote: |
| It seems that they should alter the application to get the reply from the more likely queue manager first, but if no msg. is received then try to get it from the second queue manager (depending on how the cluster distribution is configured) - so, perhaps making the one box be the likely receiver of the msg about 70% of the time, so the double gets would only be done on exception. |
This sounds a lot like you're confusing 2 concepts here. Concept 1 is the queue manager cluster, where a request can be sent to 1 of 2 clustered queue managers (and can be sent to 1 70% of the time). Concept 2 is how the application connects to a queue manager to make a request and receive a reply. In this second case you can create a configuration where the app connectes to the "most likely" queue manager by default and uses the other when it's down. This doesn't require app changes; the app should never know or care where it's connected to. Such things are WMQ issues.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
