| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| CLWL attributes not working |
« View previous topic :: View next topic » |
| Author |
Message
|
| Bravo |
 Posted: Mon Aug 10, 2009 1:06 pm Post subject: CLWL attributes not working |
 |
|
Centurion
Joined: 03 Oct 2005
Posts: 146
|
Hi All,
We have 2 FR QM's MQ V6 on Solaris 10 and 1 PR MQ V6 on AIX 5.3. All the messages are sent from PR QM to 2 FR QM's.
Based on the requirement, we defined same cluster ql on both FR QM's. We want to keep one FR as primary and another FR QM as secondary(backup).
The messages should go to secondary QM in case of primary QM failure/unavailable. As per the IBM document, we set CLWLPRTY queue attribute 9 and 0.
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.csqzah.doc/qc13010_.htm
QM1 (PR) -- AIX
QM2 (FR) -- Solaris
QM3 (FR) -- Solaris
QM2 and QM3 cluster sender and receiver chl.
QM1 is defined with cluster sender to one of the FR's QM2.
We set,
clus ql Q1 on FR QM2 with CLWL PRTY 9
clus ql Q1 on FR QM3 with CLWL PRTY 0 (default)
clusrcvr chl TO.QM2 on FR QM2 with CLWL PRTY 9
Refresh cluster on all 3 QM's.
Every first run with more than 1000 messages, we see one message is routed to clus ql Q1 on QM3 with CLWL PRTY 0 (default). Next consecutive runs with more than 1000 messages are working fine..
Am I missing something? Do I set any other workload balancing attribute to make it work?.
Any suggestions.
_________________
Bravo |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Aug 10, 2009 1:34 pm Post subject: Re: CLWL attributes not working |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Bravo wrote: |
Am I missing something? Do I set any other workload balancing attribute to make it work?.
|
You need to make sure the application is not using or inheriting BIND_ON_OPEN
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Bravo |
| Posted: Mon Aug 10, 2009 3:14 pm Post subject: |
|
|
Centurion
Joined: 03 Oct 2005
Posts: 146
|
clus ql's are defined as BIND_NOT_FIXED and the messages are coming from Message Broker to FR QM's.
_________________
Bravo |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Aug 10, 2009 3:37 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
The priority selection is made after the channel status is checked. So for you first test your channels were Inactive. When you first started putting messages, one of the channels made it from Inactive to Running before the other. The other channel was still Initializing, or binding, or starting, etc. During that time, QM1 was able to finish sending all 1000 to the channel that made it to Running first.
A channel that is not Inactive or not Running is not considered a valid target, even if it has a higher priority/rank or the queues on the QM it sends to have a higher priority or rank. Since every channel that is starting up cycles thru several intermediate stages, you will always have this problem for a brief period of time as the channels start.
You could set DISCINT to 0 for the higher priority channel so its always running, but I don't like that. And even a running channel might drop into retrying for a minute due to a network blip, causing all your messages to go to the other QM.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| sumit |
| Posted: Tue Aug 11, 2009 5:59 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
What about other configuration like CLWLWGHT on channel level, queue manager level and q level?
_________________
Regards
Sumit |
|
| 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
|
|
|
|
