MQSeries.net :: View topic - Cluster Queue Alias Name Resolution Enforcement

TZO · Posted: Thu Sep 29, 2016 5:40 am Post subject:

Hey folks,

IÂ´m facing some issues regarding name resolution in a clustered request reply szenario. One of our costumers environment is spanned over two different locations hosted by 2 different provider. On each location we got a queue manager working together in a cluster.

Now we got some request / reply scenarios where Application A sends over QMA a request to a cluster queue on QMB. Application B on QMB takes that message and writes the answer on the defined Reply Queue, which lays on QMA.

To get this happen with restricted user rights we got two options:
1.) Use an Alias Queue on QMB where to set the mqaut rights for Application BÂ´s technical user that points to the cluster reply queue on QMA.
2.) Define the Reply Queue on QMA in the cluster an give the application BÂ´s User the rights to write to the SYSTEM.CLUSTER.TRANSMIT.QUEUE

We decided to work with option 1) and defined an Alias to the clustered reply queue. This alias queue (defined on QMB) has the same name as its Base queue, which is the reply cluster queue on QMA.

Now the issue: In most of the cases the base queue resolution works fine, so that replies are send over the alias to the reply queue, but in some cases we get an baseq type error, which from my opinion could, be a hint that the alias tries to route the replies to itself as alias queue name and based name are equal.

Is there any possibility to force an alias queue, or even the queue manager to firstly resolve cluster queue names instead of local queues?