MQSeries.net :: View topic - Clients and psuedo workload balancing; or do I need Cluster

PeterPotkay · Posted: Wed Jul 03, 2002 5:52 am Post subject:

3 machines are set up identically with the same MQ application (get the request/send back the reply). The goal is to make sure that messages are processed as fast as possible.

QM1 is a spoke in our Hub and Spoke architecture. QM1 sends the original request to QMHub. From QMHub, the message goes to QM2, our client concentrator. If I set up the three application machines as MQClients, and have them all open the SAME request queue with an unlimited wait, what will happen? I assume one of the three (random?) will grab the 1st request and process it. If another request message lands before whoever grabbed the first can come back to do its get with unlimited wait again, then the remaining 2 will fight for the next message. If the all 3 are there waiting, then any of them, and possibly always the same one, will process the next message.

So while I don't have true work load balancing (at the end of the day Client1 may have got 23%, Client2, 57% and 20% the remaining, and the next day the numbers could be different), no messages were ever waiting on the request queue (unless all 3 were busy at the same time). Any pitfalls here?

Or do I need to forget the QM2 Client concentrator and go to QM1 ---> QMHub ----> Cluster1, where I install a QM on each of the 3 machines, cluster the three and then have a cluster queue called RequestQ on all 3. Will messages leaving QMHub (not in Cluster1) land in a round robin fashion on the 3 instances of RequestQ?
_________________
Peter Potkay
Keep Calm and MQ On