| Author |
Message
|
| Ward |
 Posted: Mon May 03, 2004 6:02 am Post subject: WMQI can't write to cluster queue |
 |
|
Voyager
Joined: 27 Jun 2001
Posts: 98
Location: Europe
|
We're using WMQI 2.1 on AIX. Most things go fine, but for some clustered queues trying to write to them doesn't seem to work. Strange is that for some other queues, set up totally similarly, all works great.
In the WMQI trace we get the following error message:
2004-05-03 13:39:17.023626 1800 RecoverableException BIP2604E: Node failed to open MQSeries queue 'IP_TEST_QA' owned by queue manager '': completion code 2; reason code 2085.
The queue 'IP_TEST_QA' is a clustered queue alias on our gateway QMGR A while WMQI runs on QMGR B within the same cluster. The alias resolves to a remote queue on QMGR A which is set up so messages can leave via our gateway Queue manager to "the outside world".
The cluster queue is visible in QMGR B using MQExplorer...
Has anyone seen similar behaviour ?
Thanks,
Ward. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon May 03, 2004 6:07 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
can you AMQSPUT to the cluster queue from QMGR B ?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Ward |
| Posted: Mon May 03, 2004 6:17 am Post subject: |
|
|
Voyager
Joined: 27 Jun 2001
Posts: 98
Location: Europe
|
| No, we get the same error code 2085... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon May 03, 2004 6:20 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Then the problem is not WMQI.
Try refreshing the cluster.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Ward |
| Posted: Mon May 03, 2004 7:14 am Post subject: |
|
|
Voyager
Joined: 27 Jun 2001
Posts: 98
Location: Europe
|
| and when that doesn't help ??? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon May 03, 2004 7:29 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Quote: |
The cluster queue is visible in QMGR B using MQExplorer...
|
A completely unreliable method of trying to find out what is going on with a cluster for a partial repository QM. MQExplorer cheats by making its own connection to the full repository QM and then populating the view with what it thinks you should see.
On the server running QMB, go to the command prompt and issue the following command from a runmqsc session:
dis qcluster(IP_TEST_QA)
What does it show?
Also, a refresh on QMB only PUSHES out QMB's info to the FR, it will not PULL in anything to QMB.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Ward |
| Posted: Mon May 03, 2004 8:00 am Post subject: |
|
|
Voyager
Joined: 27 Jun 2001
Posts: 98
Location: Europe
|
Didn't trust the MQExplorer on that either and tried the dis qcluster before... giving me all the info as expected (incl CLUSQMGR QMGR A)...
Then I tried the "microsoft" solution... deleted and recreated the cluster queue (using nothing but copy & paste) and guess what: all works fine now ! Scary !
Don't understand it at all, but at least it's not blocking us anymore...
Thanks for all the help !
Cheers,
Ward. |
|
| Back to top |
|
|
|
|
