| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Cluster resolution error... |
« View previous topic :: View next topic » |
| Author |
Message
|
| duffMan |
 Posted: Mon Mar 12, 2007 8:19 am Post subject: Cluster resolution error... |
 |
|
Voyager
Joined: 03 Jun 2002
Posts: 75
|
I'm sure this has been asked before but here it goes again....
I have 3 queue managers, A B and C.
Between A and B is a regular sender channel.
B and C are clustered.
QA1 is defined as a clustered alias queue on C in the BC cluster, which resolves to a local q QL1 on C.
QR1 is a remote queue on A which has a rqname of QA1 and rqmname of B.
I would expect doing an amqsput of a sample message on A to go to B and be resolved there to go to the clustered alias queue QA1 on C and finally end up on QL1 on C....but this is not happening.
The message is ending up on the dead letter queue on B with a 2085.
When I put to QA1 from B using amqsput it works fine.
Are there some queue resolution logic that I am missing here?
We are running at 5.3 csd13. All queue are defined as NOTFIXED for defbind (if that matters).
Thanks. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Mar 12, 2007 8:27 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
If the remote queue definition specifies a queue manager (in this case B) then MQ will try to resolve the queue name on that queue manager.
You're right, this has been discussed many times before. I would search for "gateway queue managers", "cluster aliases" and check out the Clustering manual which IIRC (and I may not) talks through an example similar to this.
Basically you need to send the message to the cluster, not a specific queue manager which happens to be clustered, to achieve the result you're looking for.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| duffMan |
| Posted: Mon Mar 12, 2007 9:10 am Post subject: |
|
|
Voyager
Joined: 03 Jun 2002
Posts: 75
|
thanks....that hit the spot...I found related posting.
the mq admin defined the queue manager alias incorrectly. Rather than leave the rqmname blank they put the queue manager B.
again thanks for the suggestion! |
|
| 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
|
|
|
|
