| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| how to reset the initial list of order from CCDT? |
« View previous topic :: View next topic » |
| Author |
Message
|
| mchan |
 Posted: Wed Oct 05, 2011 10:19 pm Post subject: how to reset the initial list of order from CCDT? |
 |
|
Apprentice
Joined: 09 Sep 2011
Posts: 29
|
I read from the following link:
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzaf.doc/cs12990_.htm
| Quote: |
It is important to note that, with AFFINITY(PREFERRED), each time this particular client machine connects it will place the channels in the same initial order of preference. This applies even when the connections are from different processes or at different times.
|
If I understand correctly, different processes, even if they used different CCDT, they will following the same ordering defined earlier when CCDT is first use.
E.g.,
I have 2 MQv7 JMS client app which used CCDTs.
App_A uses CCDT_A and App_B uses CCDT_B. They are running on the same client machine.
Let say CCDT_A and CCDT_B are as follow:
CCDT_A:
| Quote: |
-- QM1 under QMGROUP1
DEFINE CHANNEL(QMGROUP1.A) CHLTYPE(CLNTCONN) TRPTYPE(TCP) +
CONNAME('HOST1(61001)') QMNAME(QMGROUP1) AFFINITY(PREFERRED) CLNTWGHT(9) REPLACE
-- QM2 under QMGROUP1
DEFINE CHANNEL(QMGROUP1.B) CHLTYPE(CLNTCONN) TRPTYPE(TCP) +
CONNAME('HOST1(61002)') QMNAME(QMGROUP1) AFFINITY(PREFERRED) CLNTWGHT(1) REPLACE
|
CCDT_B
| Quote: |
-- QM1 under QMGROUP1
DEFINE CHANNEL(QMGROUP1.A) CHLTYPE(CLNTCONN) TRPTYPE(TCP) +
CONNAME('HOST1(61001)') QMNAME(QMGROUP1) AFFINITY(PREFERRED) CLNTWGHT(1) REPLACE
-- QM2 under QMGROUP1
DEFINE CHANNEL(QMGROUP1.B) CHLTYPE(CLNTCONN) TRPTYPE(TCP) +
CONNAME('HOST1(61002)') QMNAME(QMGROUP1) AFFINITY(PREFERRED) CLNTWGHT(9) REPLACE
|
The 2 CCDT differs only on the respective weighting (9:1 vs 1:9)
At the very first time, I try App_B and all the message goes to QM2.
When I later try App_A, all the message still goes to QM2.
I think this is because of AFFINITY(PREFERRED), each time this particular client machine connects it will place the channels in the same initial order of preference.
If this is so but I want to keep AFFINITY(PREFERRED), how do I RESET the "initial order of preference" such that all the message goes to QM1?
In other words, where is "initial order of preference" stored and how can we reset it?
Thanks! |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Oct 06, 2011 1:35 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
First, there are other channel attributes used in the selection of the next channel definition.
I recommend that you read the relevant sections of the WMQ MQSC and Intercommunications manuasl that deal with client-channel attributes.
Part of channel selection criteria (that most often works) is that the channel most recently used will most likely be useful for the next connection - QM2 in your case.
Someone from the IBM WMQ factory will be wandering by shortly, and may have an answer for you.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mchan |
| Posted: Thu Oct 06, 2011 7:25 pm Post subject: |
|
|
Apprentice
Joined: 09 Sep 2011
Posts: 29
|
I want to further clarify a little bit on the CCDT. In other words,
is AFFINITY option and CLNTWGHT mutually exclusive?
In other words, once we defined AFFINITY(PREFERRED), any CLNTGHT defined along will be ignored?
If I want the same client process to have
- load balancing to different MQ on its first MQ connection (first qcf.createQueueConnection()) according to CLNTWGHT
- stick to the same MQ on subsequent MQ connection.
There is no way in v7 CCDT for this, right?
So, is PREFERRED just a backward compatible way for v6, where connection ordering will be based on alphabetical order of channel names?
but, having CLNTGHT(0) already cater this, right? |
|
| Back to top |
|
|
| mchan |
| Posted: Tue Oct 11, 2011 5:39 pm Post subject: |
|
|
Apprentice
Joined: 09 Sep 2011
Posts: 29
|
| Any one has clue with my questions above? I am stucked and can proceed further. Many thanks for your help! |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Oct 11, 2011 6:44 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
You have posed a hypothetical. What exactly is the problem?
What have you tried? What were the results? Did your results comply with IBM documentation on how channels are selected? Did you test with one message, one client? 1,000 messages, 1,000 clients?
Why are you stuck? What is it about your applications that the v7 channel attributes don't satisfy? Are your apps failing to meet SLAs? Or, is this just an intellectual exercise?
| Quote: |
| where is "initial order of preference" stored and how can we reset it? |
Perhaps you should open a PMR with IBM on this.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Oct 11, 2011 8:26 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Oct 12, 2011 3:33 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
While we appreciate your curiosity, you have become target-locked on minutia.
The channel attributes provided with v7 should adequately address most, if not all, workload requirements.
The documentation clearly states that the channel selection algorithm is not a guarantee of exactly how, where, and how many messages will be delivered.
A user-written cluster workload exit remains available if you are not satisfied with what IBM channel attributes offer.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| 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
|
|
|
|
