Author |
Message
|
Yannanlu |
Posted: Thu Jan 16, 2003 6:55 am Post subject: Can a xmitq attached to two active channels? |
|
|
Apprentice
Joined: 23 Jan 2002 Posts: 27
|
We are planning to set up load balance on the MQ network without implementing cluster. I am wondering if we can have two active channels share the same xmitq. If yes, we will have these two channels to do the load balance. Otherwise, we have to write our own channel exit for this purpose.
Any comment and suggestion will be appreciated.
Yannan |
|
Back to top |
|
 |
mqonnet |
Posted: Thu Jan 16, 2003 7:54 am Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
My understanding is that each channel(irrespective of type) opens the Xmitq, "exclusively", and hence there is no way you could have more than one channel point to the same xmitq. You could, but you cannot run both the channels at the same time.
Cheers.
Kumar _________________ IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
Back to top |
|
 |
Yannanlu |
Posted: Thu Jan 16, 2003 8:09 am Post subject: |
|
|
Apprentice
Joined: 23 Jan 2002 Posts: 27
|
Thank for your reply. As you said that, is there any way to work around it?
How about to have two active channels sharing the same cluster xmitq in a cluster env?
As you know, in order to use load balance feature of a clustering, you have to have a cluster member that has no local queue for the target queue. This entry-point qmgr is a single-point failure. In our env, we have to have multiple entry-point qmgrs. This will increase the size of the cluster and increase the overhead.
Do you have any suggestions?
Thannks again,
Yannan |
|
Back to top |
|
 |
mqonnet |
Posted: Thu Jan 16, 2003 11:15 am Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
Could you be more specific on your problem. I am unable to follow what you are upto.
Load balancing is done by MQ, you dont need to do anything. The simplest scenario for clustering is, say you have 2 Full repository and 2 partial repos. In the event of failure of any one of them, the failure info is shared between the rest of the active repos and they just carry on from there.
What's the point of having to point 2 channels to a single xmitq(be it regular or cluster chls). You could as well have 2 xmitqs. Xmitq's dont determine the entry points, its the MCA's. So in all cases, the xmitq is masked off.
Hope this helps
Cheers.
Kumar _________________ IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
Back to top |
|
 |
yaakovd |
Posted: Mon Jan 20, 2003 3:06 pm Post subject: |
|
|
Partisan
Joined: 20 Jan 2003 Posts: 319 Location: Israel
|
Yes, you can use blank channel in XMitQ and define multiple channels for this Queue. But in this case you cannot use triggering - it should be "OFF".
Then you can start wanted channel manually or using command.
Additional point: I guess inyour remote Q you defined primary QMgr, so on secondary QMgr you must have alias with name like primary to itself.
You must have exactly understanding of this point when you planning load ballancing. _________________ Best regards.
Yaakov
SWG, IBM Commerce, Israel |
|
Back to top |
|
 |
leongor |
Posted: Tue Jan 21, 2003 2:25 am Post subject: |
|
|
 Master
Joined: 13 May 2002 Posts: 264 Location: Israel
|
Hi Yaakov,
What you say it'll work for one of the two channels in the time.
The question was about two active channels sharing same xmitQ,
that cannot be done. _________________ Regards.
Leonid.
IBM Certified MQSeries Specialist. |
|
Back to top |
|
 |
yaakovd |
Posted: Tue Jan 21, 2003 4:16 am Post subject: |
|
|
Partisan
Joined: 20 Jan 2003 Posts: 319 Location: Israel
|
Of course, you are right. I recognized this point later
Actually, my point was arround this topic - just additional think... _________________ Best regards.
Yaakov
SWG, IBM Commerce, Israel |
|
Back to top |
|
 |
|