| Author |
Message
|
| sunnybab |
 Posted: Sun Feb 05, 2006 4:35 pm Post subject: Workload Balancing in MQ 6.0 |
 |
|
Novice
Joined: 12 Jan 2006
Posts: 21
|
Hi all,
I have Question on Work load Balancing Alogorithms and sequence'ng on WebSphere MQ V6.0.
I am running WebSphere MQ V6.0 on two Solaris Servers ( server1 and server2) - MQ CLuster both have Full repos.
Server 1 hosts Queue Manager QM1 with CLQ Queue1 ( CLuster Local Queue)
Server 2 hosts Queue Manager QM2 with CLQ Queue1 ( Cluster Local Queue)
Remote Client connect to Server 1 QM1 using SYSTEM.DEF.SVRCONN and puts messge to server 1 Queue 1.
Both Server 1 and server 2 have WebSphere Application installed and can process the message.
The Problem is that all the messages need to be processed in Sequence (FIFO) as they have dependencies on each other.
So the option I was looking at is Changing the cluster workload rank (CLWLRANK) attribute on the cluster receiver channel of Server 1 higher than Server 2 So all the messages go to Server 1 and get processed by WebSphere Application in there and for some reason Server 1 goes down ..Messages will go to Server 2 since that is the only Server left though with lower Rank and get processed by WebSphere Application on Server 2.
I tried this option setting CLWLRANK=2 on Server 1 Rcvr channel and CLWLRANK= 1 on Server 2 , all messages go to Server 1 which works fine. Problem is when I tried shutting down QM1 Queue Manager and Listener on server1 ,ideally all messages should go to server 2 QM2 but messages don't go to Server 2 .. and when I bring back up the Queue Manager Qm1 ..All the messages I sent appear back on QM1..
Any Ideas ? what could be wrong here ? why they not going to Qm2 ..
or Any other option you guys can suggest which will work in this scenario to maintain sequence between 2 servers?
Thanks in advance |
|
| Back to top |
|
 |
| vennela |
| Posted: Sun Feb 05, 2006 5:54 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Though the QMGRs are in cluster, you are not using any clustering features here.
If the application connects to a QMGR with one of the cluster queues hosted on it (irrespective of the weight you give it), all the messages go to the QMGR you are connected to. The other QMGRs will not get messages.
Now, if had a 3rd QMGR like a gateway, clustered along with these QMGRs and if your app connected to that QMGR, then clustering becomes effective. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Feb 05, 2006 7:39 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Have you defined the clusterqueues with the CLWL.... to ANY or QMGR?
Make sure as well that you open the queue with bind on open.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sunnybab |
| Posted: Sun Feb 05, 2006 8:02 pm Post subject: |
|
|
Novice
Joined: 12 Jan 2006
Posts: 21
|
| fjb_saper wrote: |
Have you defined the clusterqueues with the CLWL.... to ANY or QMGR?
Make sure as well that you open the queue with bind on open.
Enjoy |
CLWLUSEQ is set to QMGR , I even tried ANY , DEFBIND is OPEN |
|
| Back to top |
|
|
| vennela |
| Posted: Sun Feb 05, 2006 8:51 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| sunnybab wrote: |
| fjb_saper wrote: |
Have you defined the clusterqueues with the CLWL.... to ANY or QMGR?
Make sure as well that you open the queue with bind on open.
Enjoy |
CLWLUSEQ is set to QMGR , I even tried ANY , DEFBIND is OPEN |
Whatever, as long as you don't have a gateway, it's not gonna help. |
|
| Back to top |
|
|
| sunnybab |
| Posted: Sun Feb 05, 2006 10:26 pm Post subject: |
|
|
Novice
Joined: 12 Jan 2006
Posts: 21
|
| vennela wrote: |
| sunnybab wrote: |
| fjb_saper wrote: |
Have you defined the clusterqueues with the CLWL.... to ANY or QMGR?
Make sure as well that you open the queue with bind on open.
Enjoy |
CLWLUSEQ is set to QMGR , I even tried ANY , DEFBIND is OPEN |
Whatever, as long as you don't have a gateway, it's not gonna help. |
Thanks , you mean If a setup another Queue Manager QM3 on same or separate server , make it part of same cluster and use it gateway - problem of redirect to lower Rank Queue Manager will be resolved ?
another question is what if my QM3 goes down which is my gateway to Qm1 and Qm2. |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Feb 06, 2006 3:51 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| sunnybab wrote: |
another question is what if my QM3 goes down which is my gateway to Qm1 and Qm2. |
That is one of the reasons why they say MQ Clustering is just load balancing but not true failover.
You have to use some hardware clustering to circumvent this. |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Tue Feb 07, 2006 12:25 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
See also the thread
| Quote: |
| MQ 5.3 Linux Clustering Pro's & Con's |
in this forum. The mechanisms are the same - exept of some more attributes in V6, which extend the load balancing machanisms.
_________________
Regards
Hubert |
|
| Back to top |
|
|
|
|
