Author |
Message
|
HenriqueS |
Posted: Fri Mar 05, 2010 1:40 pm Post subject: Remote qmgr name and xmitq name must match ? |
|
|
 Master
Joined: 22 Sep 2006 Posts: 235
|
I had an error that is not very well documented (2 google hits only!), called MQ_UNKNOWN _DEF_XMIT_Q while trying to establish a sender-receiver channel with a business partner.
This error shows up in the DLQ reason descriptors for the messages sent from my side to the partner (the messages went straight to the partner DLQ).
I solved this by advising my partner to create an queue manager alias named as my xmitq name and pointing ('remote queue manager' attribute) to her real qmgr name.
I still not realize what really happened...does the remote qmgr name and my xmitq name (the one attached to my sender channel) must match ? I never noticed this... |
|
Back to top |
|
 |
mvic |
Posted: Fri Mar 05, 2010 1:47 pm Post subject: Re: Remote qmgr name and xmitq name must match ? |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
|
Back to top |
|
 |
Vitor |
Posted: Fri Mar 05, 2010 1:52 pm Post subject: Re: Remote qmgr name and xmitq name must match ? |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
HenriqueS wrote: |
I still not realize what really happened...does the remote qmgr name and my xmitq name (the one attached to my sender channel) must match ? I never noticed this... |
It is documented.
If the remote queue definition does not explicitly name a transmission queue then the queue manager will try to find a queue with the same name as the remote queue manager. If that fails, it will try and use the default transmission queue for the local queue manager.
So your partner could have equally solved the problem by specifying a transmission queue. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
HenriqueS |
Posted: Fri Mar 05, 2010 2:20 pm Post subject: Re: Remote qmgr name and xmitq name must match ? |
|
|
 Master
Joined: 22 Sep 2006 Posts: 235
|
My remote queue definition that points to the partner is set with a transmission queue (let´s say QM.123) defined locally in my qmgr and referenced by my sender channel.
The same remote queue definition is set also with a remote qmgr name called 'QM.123'.
But in the partner side the qmgr name differs from QM.123. That´s why I asked them to create the qmgr alias in their side to point 'QM.123' to their real qmgr name.
Maybe if I did left blank the remote qmgr name attribute in my remote queue definition this would not happen and they would not have to create a qmgre alias in their side?
Vitor wrote: |
HenriqueS wrote: |
I still not realize what really happened...does the remote qmgr name and my xmitq name (the one attached to my sender channel) must match ? I never noticed this... |
It is documented.
If the remote queue definition does not explicitly name a transmission queue then the queue manager will try to find a queue with the same name as the remote queue manager. If that fails, it will try and use the default transmission queue for the local queue manager.
So your partner could have equally solved the problem by specifying a transmission queue. |
|
|
Back to top |
|
 |
Vitor |
Posted: Fri Mar 05, 2010 2:35 pm Post subject: Re: Remote qmgr name and xmitq name must match ? |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
HenriqueS wrote: |
The same remote queue definition is set also with a remote qmgr name called 'QM.123'. |
Why is this not the name of the queue manager the target queue lives on? Why is this QM.123 not the partner's queue manager name? That is what the field is for if you look at the documentation. You could still quote the transmission queue name of QM.123 if that's how the message reaches that queue manager. In this way the message would arrive properly addressed and no alias is needed.
HenriqueS wrote: |
Maybe if I did left blank the remote qmgr name attribute in my remote queue definition this would not happen and they would not have to create a qmgre alias in their side? |
No, it would just look for a queue manager called blank. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Michael Dag |
Posted: Sat Mar 06, 2010 6:22 am Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
on a QREMOTE definition the RQMNAME must match the name of the Qmgr on the other end or there must be a QMgr Alias on the other end or there must be a Transmission Queue with that name on the other end...
The name of the transmission Queue on your end if named on both QREMOTE and CHANNEL is totally irrellevant and can be named anything...
but why did you set the RQMNAME to something different then the name on the other end? _________________ Michael
MQSystems Facebook page |
|
Back to top |
|
 |
|