| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| COD in Clustering ??? |
« View previous topic :: View next topic » |
| Author |
Message
|
| abiram8 |
 Posted: Fri Dec 19, 2003 12:06 am Post subject: COD in Clustering ??? |
 |
|
Master
Joined: 27 Mar 2002
Posts: 207
Location: India
|
Hi,
I have Queue Manager QM1 (Full Repository Manager in host H1) and put msg to Cluster queue (QM2.[SHARE.Q] in Host2 Full Repository ) which is not in QM1.
The Queue Manager QM2(in host H1) have a Cluster queue named SHARE.Q
Note: QM1 donot have the cluster queue SHARE.Q
My Client in host of QM1 and puts the message to SHARE.Q (of QM2) with COD option in message.
I have defined required parameter and the MQObject for COD but my Reply to Queue (QM1.Reply) never get information even when the application takes message from QM2.(SHARE.Q).
But the same set up works when I use COA option
My queue QM1.Reply gets the ionformation that the message reached the
QM1.(SHARE.Q).
But I donot know Why COD option did not work.
Is it so that COD will not work for Cluster .
 |
|
| Back to top |
|
 |
| EddieA |
| Posted: Fri Dec 19, 2003 9:30 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
That looks like it should work. There's no difference, that I know, in sending replies to COA and COD.
Did you look in the DLQ on QM2. If the message couldn't be put for some reason, that's where it will be.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Dec 19, 2003 2:58 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7717
|
When the COA message is generated, it is put with the same authority as the putter of the original message.
Unless you are running your RCVR channel with the MCAUSER value set to something other than blank, the RCVR is running with the ID that started it, "mqm". "mqm" has full authority to do any put on any system, so it works and the COA message gets sent.
When the COD message is generated, it is put with the same authority as the MQMD.UserIdentifier of the original message.
Looks like that ID does not have authority on your remote system, so the put of the COD fails with a 2035 RC. They will be in the DLQ, and the DLH will have the 2035 code.
CODs work just fine in a cluster. You just have to give the prper IDs the proper authority.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
