|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
MQ Client with QMGR Cluster |
« View previous topic :: View next topic » |
Author |
Message
|
raghubegur |
Posted: Wed Jan 17, 2007 10:57 am Post subject: MQ Client with QMGR Cluster |
|
|
Apprentice
Joined: 15 Jul 2002 Posts: 45
|
Hi,
We have 3 QMGRs clustered : QM1, QM2 and QM3.
QM1 and QM2 are Gateway QMGRs.
QM3 hosts a message broker.
We have a MQ client that has to send and receive messages from QM3. But it can connect only to the gateway QMGRs.
What is the best approach for a MQ Client to exploit the available cluster ( load balancing ) ? Is it possible ?
We are NOT allowed to have distributed queuing from gateway QMGRs to QM3. _________________ Cheers
Raghu |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Jan 17, 2007 11:07 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Gateway QMGrs must host as qlocals any queues that the clients need to GET from.
Other than that, you're fine. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
raghubegur |
Posted: Wed Jan 17, 2007 11:33 am Post subject: |
|
|
Apprentice
Joined: 15 Jul 2002 Posts: 45
|
Does it mean when the client does a PUT to a cluster queue ( which it does via MQServer variable or CHLTAB) the cluster advantages of load balancing and failover are available ?
At any point in time, the client will be connected to one of the gateway QMGRs. So the response message for the client should be available on the QLOCAL of the QMGR to which it has the connection. That would mean that QM3 has to send the response message to QLOCAL on the gateway QMGRs. --> Back to Distributed queues.
Also, we need to keep ReplyToQMGR information. This again may have a problem because PUT on a cluster queue could mean the request message can be routed by either QM1 or QM2. ReplyToQMGR can be a QMGR on which the client is not polling. _________________ Cheers
Raghu |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Jan 17, 2007 11:45 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
ReplyToQmgr should always be set by the replying application based on the value in the MQMD of the request. This should always be the right queue manager.
If this is done, then the put will not be load balanced across the cluster.
The MQReply node does the right thing in this case.
The MQServer variable and CHLTAB variables define which queue manager the client will connect to. PUTS don't get affected by that - but normal cluster workload balancing does apply to all PUTs by any MQ application. _________________ I am *not* the model of the modern major general. |
|
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
|
|
|
|