| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Putting message across clusters |
« View previous topic :: View next topic » |
| Author |
Message
|
| PaulHuang |
 Posted: Wed Aug 01, 2001 10:33 pm Post subject: |
 |
|
Novice
Joined: 31 Jul 2001
Posts: 18
|
hello
I have encountered a problem while putting messages across clusters.
I have three queue managers A, B and C where A and B joined one cluster
called Cluster1
while B and C joined one cluster called Cluster2. The goal is to put a
message from queue manager
A to a cluster queue in Queue manager C. After refering to the
instruction provided in red book
i've defined an alias queue in queue manager B resolving to the cluster
queue in queue manager C,
and this alias queue belongs to cluster CLUSTER1 so it is visible at queue manager
A.
but when I put a message at Queue manager B using this alias queue, I've
notice the message is routed
to SYSTEM.DEAD.LETTER.QUEUE at Queue manager B with DLH showing 2082 as
the reason code.
Do you have any idea what may of gone wrong? If I put the message using
this alias queue at Queue Manager
B, I can send the message to cluster queue at Queue manager C
successfully.
Thanks in advance for any hints or tips!
|
|
| Back to top |
|
 |
| bduncan |
| Posted: Thu Aug 02, 2001 3:41 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
So for anyone who doesn't have the MQSeries Manuals nearby, a 2082 is MQRC_UNKNOWN_ALIAS_BASE_Q.
It's hard to say exactly what your issue is, because I don't have your exact QALIAS definition to look at. But my best guess is that you have left out the all important CLUSTER parameter in your definition of the alias queue. In order for other Queue Managers to resolve the QALIAS that you've defined, you must instruct the Queue Manager hosting the QALIAS definition to advertise the QALIAS to one of the clusters it belongs to. In other words, if Queue Manager A belongs to clusters "ONE" and "TWO", then when I define a QALIAS on A, I need to tell it whether to advertise the QALIAS to members of "ONE", "TWO", both, or neither. For instance:
DEFINE QALIAS(REDIRECT) TARGQ(TEST) CLUSTER(ONE)
If I neglect to leave out the CLUSTER parameter and simply say:
DEFINE QALIAS(REDIRECT) TARGQ(TEST)
Then the QALIAS definition will not be advertised to any of the clusters that A is a member of, and therefore it will only work for applications on A itself, or Queue Managers that are connect to A via static channels and are using remote queue definitions. But other clustered queue managers would definitely get a 2082, because the QALIAS definition is not being advertised in any clusters...
If this doesn't fix your problem, please post the exact QALIAS definition so we can better diagnose the problem. Thanks...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| Reddiough |
| Posted: Mon Aug 06, 2001 12:39 am Post subject: |
|
|
Novice
Joined: 27 Jun 2001
Posts: 23
|
Try changing the default bind option on the alias queue definition to bind not fixed.
Not only is this in the red book, but it was also in the manual as an example of bridging queue managers.
I hit exactly the same thing as you about a year ago on 5.1 and I raised it with IBM. They came back and told me it worked so long as you have the bind not fixed option set.
I told them that this didn't make much sense but they couldn't understand the problem.
They said they would update the manual to make this clearer.
By the way, the second example in the book, using a queue manager alias works a treat. So does the example using ANY.MANAGER as a generic queue manager alias. This works better and is very powerful. |
|
| 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
|
|
|
|
