| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Clustering Architecture Validation |
« View previous topic :: View next topic » |
| Author |
Message
|
| orangeSweep |
 Posted: Sat Sep 19, 2009 4:52 am Post subject: Clustering Architecture Validation |
 |
|
Newbie
Joined: 19 Sep 2009
Posts: 1
|
Just trying to get feedback if this is the proper way of doing things....
We have a MQ cluster on a physical box.
Cluster has 2 Queue Managers defined, each with a queue called QUEUE1
We have a Websphere/WebLogic (undecided for now, not sure if it matters for this discussion, but if it does, please let me know) cluster on seperate boxes, each box has it's own Websphere/Weblogic server.
When a messages comes into the MQ Cluster for QUEUE1, the message is load balanced between the 2 Queue Managers.
Here is where I have questions:
How does the appserver cluster get to load balance the messages? On the appserver it is a straight read from the queue, so I would setup a MDB to read off of QUEUE1.
Is this where I would need to specify a CCDT at the ConnectionFactory configuration on each app server and let it decide which queue manager to read from? Once it attaches to that queue manager will it always use that queue manager for reading until it fails and only then fail over? If that is the case, then I could potentially have all the appservers attaching to the same queue manager and the other queue manager will not have messages being drained.
Thanks for any help! |
|
| Back to top |
|
 |
| Vitor |
| Posted: Sat Sep 19, 2009 8:57 am Post subject: Re: Clustering Architecture Validation |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| orangeSweep wrote: |
| How does the appserver cluster get to load balance the messages? On the appserver it is a straight read from the queue, so I would setup a MDB to read off of QUEUE1. |
If you're using a WMQ cluster to load balance the messages, why do you want the app server to load balance the messages as well? Once the message has been delivered to whichever QUEUE1, the WMQ cluster is irrelevant and the app server reads the message in whatever way it would otherwise, with all the possibilites like mulit-threading and so forth.
| orangeSweep wrote: |
| Is this where I would need to specify a CCDT at the ConnectionFactory configuration on each app server and let it decide which queue manager to read from? |
Yes.
| orangeSweep wrote: |
| Once it attaches to that queue manager will it always use that queue manager for reading until it fails and only then fail over? |
Yes
| orangeSweep wrote: |
| If that is the case, then I could potentially have all the appservers attaching to the same queue manager and the other queue manager will not have messages being drained. |
Yes.
This is why WMQ clusters are unsuitable for HA failover.
_________________
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
|
|
|
|
