|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Queue manager name resolution happening incorrect |
« View previous topic :: View next topic » |
Author |
Message
|
knock2mq |
Posted: Sun Jan 24, 2010 8:31 pm Post subject: Queue manager name resolution happening incorrect |
|
|
Novice
Joined: 09 Jan 2010 Posts: 17
|
Hi All,
In my MQ-Windows environment, I am testing Qmgr name resolution for outbound messages. Below are the definitions:
1. On QMGR2, I created a Remote Q def having RemoteQName=<blank>, RemoteQMName=QMGR3, TXQName=<blank>
So I think this is where queue manager name resolution happening.
2. On QMGR3, there is a local queue TESTQ.
3. On command prompt, I am writing below:
AMQSPUT TESTQ QMGR2
But getting 2087 error.
4. Both qmgrs are on same machine.
5. Channels, tx q exist between both queue managers.
Please advise why queue manager name resolution not working. |
|
Back to top |
|
 |
fjb_saper |
Posted: Sun Jan 24, 2010 8:57 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
a) You're not in a cluster (hint, hint)
b) intercommunications manual you did not follow it (hint)
c) working as designed...
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
bruce2359 |
Posted: Sun Jan 24, 2010 9:17 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Quote: |
1. On QMGR2, I created a Remote Q def having RemoteQName=<blank>, RemoteQMName=QMGR3, TXQName=<blank> |
How about displaying all relevant object definitions with all of the attributes so we can see exactly what you have done? For example: DISPLAY QR(whatever you called your object) ALL. Then post the results here. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
Vitor |
Posted: Mon Jan 25, 2010 6:05 am Post subject: Re: Queue manager name resolution happening incorrect |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
knock2mq wrote: |
1. On QMGR2, I created a Remote Q def having RemoteQName=<blank>, RemoteQMName=QMGR3, TXQName=<blank>
So I think this is where queue manager name resolution happening. |
Yes
knock2mq wrote: |
2. On QMGR3, there is a local queue TESTQ. |
Yes
knock2mq wrote: |
3. On command prompt, I am writing below:
AMQSPUT TESTQ QMGR2
But getting 2087 error. |
Which means what, and indicates what? As a possible problem?
knock2mq wrote: |
4. Both qmgrs are on same machine. |
Irrelevant. Neither queue manager would know that
knock2mq wrote: |
5. Channels, tx q exist between both queue managers. |
But there's something important about these which the documentation talks about & I suspect you've missed.
knock2mq wrote: |
Please advise why queue manager name resolution not working. |
Because there's a problem with your configuration. Follow the advise of my associate, recheck your configuration against the documentation and think about his hint - what does a cluster do for you that you need to set up here? Think especially about what that reason code is telling you.
 _________________ Honesty is the best policy.
Insanity is the best defence. |
|
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
|
|
|
|