| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Alias and cluster |
« View previous topic :: View next topic » |
| Author |
Message
|
| Carla Viragh |
 Posted: Fri Dec 26, 2003 10:45 am Post subject: Alias and cluster |
 |
|
Voyager
Joined: 31 Oct 2003
Posts: 92
Location: São Paulo - Brasil
|
Hello all. I have a question...
I will try to simplify what is going on.
Let´s suppose we have 3 QM, QM1, QM2 and QM3 all belong to cluster CLUSTER.
QM2 hosts a local queue called QL.CLUSTER.QM2 and it´s shared in cluster CLUSTER.
QM3 hosts a alias queue called QL.CLUSTER and this alias resolves to QL.CLUSTER.QM2 and it´s shared in cluster CLUSTER too.
Right...
If I try to put a message AMQSPUT QL.CLUSTER QM1, the message goes to QM3´s DLQ and the reason code is AMQ2082.
If I try to put a message AMQSPUT QL.CLUSTER QM3, the message goes to QL.CLUSTER.QM2, the alias is resolving like expected.
Why it can´t resolve the alias if I try to put a message from QM1? Cluster is working fine, once the channels are running and the message can reach QM3, and the reason code is clear saing that the BaseQName is not correct... but... If it was not, it could not reach the queue when putting from QM3!
The queue QL.CLUSTER.QM2 can receive messages directly from QM1 and QM3 with no problems.
Does anybody know what is going on?
_________________
Carla Viragh |
|
| Back to top |
|
 |
| oz1ccg |
| Posted: Fri Dec 26, 2003 12:47 pm Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
Hi Carla,
<< I've not looked it up in the cluster book, and not tried it >>
try open the queue with BIND(NOT_FIXED), this is because QM1 can't direcly send the message to QM2, it will be send over QM3, and QM1 can't open the whole way in BIND(ON_OPEN).
The description on this is that QM3 actts as an "gateway".
Why have you created the alias on QM3 and not on QM2 ??
When you want to use a gateway it's typicly for entering a cluster, and not for inside usage.
Just my $0.02 
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sat Dec 27, 2003 7:49 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Jørgen is correct. It is the BIND option for the ALIAS queue. Set it to NOT_FIXED and you will work just fine.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Carla Viragh |
| Posted: Mon Dec 29, 2003 9:32 am Post subject: |
|
|
Voyager
Joined: 31 Oct 2003
Posts: 92
Location: São Paulo - Brasil
|
Ok, I am not a programmer but I can try to change the program.
But, if we think as administrators, my QM QM3 should look at the message, should know that it is destined to a queue that is shared in cluster, but it can´t... Why?
_________________
Carla Viragh |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Mon Dec 29, 2003 3:00 pm Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
Hi,
the problem is not MQ3.... It's QM1!!
reason: When an application on QM1 opens the queue with BIND(ON_OPEN), it requires that all send messages go to the same target queue. But QM1 don't know anything about the real target queues, just an alias on QM3. This leads to the failure...
But once again, why is the alias placed on OM3 and not on QM2 where the queue is located ??? I can't figure it out ?? design apperns ?? Just wondering 
Just my $0.02
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Dec 29, 2003 6:17 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Carla, I am willing to bet that your program simply opens the queue with whatever its default bind option is, and that the queue is still at the default of BIND_ON_OPEN. Change that queue attribute to NOT_FIXED, and you should be OK. Of course, it is possible that the program is specifically asking for BIND_ON_OPEN, in which case you will need to change the logic in the program.
Jorgen, as for why the Alias is where it is, who knows? And who cares? It should work either way. Maybe there is an app local to that machine connecting to that QM directly, and Carla for whatever reason does not want the app to know the real queue name. There is no "gateway" concept happening here.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Carla Viragh |
| Posted: Tue Dec 30, 2003 3:45 am Post subject: |
|
|
Voyager
Joined: 31 Oct 2003
Posts: 92
Location: São Paulo - Brasil
|
Hello Peter and Jorgen, thanks for your help!
The reason why I am trying to route the message through QM3 is to know the usage of cluster. I will need to know cluster very well because I will bild a big project... I must be prepared and probably I will need to do something very close to this configurations in a part of the project. Peter, you are right, the app that we have today was made by other company and we don´t want to call them again, I need to find a way to this local app to work. See? I will not use amqsput to do this 
I have read in cluster manual something about the NOT_FIXED attribute. Now I know what happened.
Thanks again!
_________________
Carla Viragh |
|
| 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
|
|
|
|
