| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| question about report option MQ6 |
« View previous topic :: View next topic » |
| Author |
Message
|
| DTran |
 Posted: Thu Feb 21, 2008 4:14 am Post subject: |
 |
|
Acolyte
Joined: 11 May 2006
Posts: 62
Location: Amsterdam
|
Hi Mr Butcher,
You have confused me  because my COD fails with my id in the MQMD. Now I will rout the message via the Broker and see if the COD can be send to the sender application.
Thnx all for your input.
Grz,
Tran
_________________
There are 10 types of people in this world - those who understand binary and those who don't |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Feb 21, 2008 7:01 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
In the request-reply model, authority is needed on both the requesting AND replying qmgrs.
I'd guess that your COD messages are in the replying qmgrs dead-letter-queue.
Edit the replying qmgrs error log file. Find 2035, and look at the identity of the failing entity. That entity must be in the security domain of the replying qmgr.
I did a quick test to simulate your environment. Two qmgrs on different Windows images. mq05 is the requesting username. Replies and COAs were returned just fine; CODs to the DLQ of the replying qmgr.
This is from the replying qmgr error log:
2/20/2008 10:32:54 - Process(3520.32) User(MUSR_MQADMIN) Program(amqzlaa0.exe)
AMQ7310: Report message could not be put on a reply-to queue.
EXPLANATION:
The attempt to put a report message on queue AMQ.47BC6CEA03160020 on queue
manager QM1 failed with reason code 2035. The message will be put on the
dead-letter queue.
ACTION:
Ensure that the reply-to queue is available and operational.
----- amqkrpta.c : 473 --------------------------------------------------------
2/20/2008 10:32:54 - Process(3520.32) User(MUSR_MQADMIN) Program(amqzlaa0.exe)
AMQ8075: Authorization failed because the SID for entity 'mq05' cannot be
obtained.
EXPLANATION:
The Object Authority Manager was unable to obtain a SID for the specified
entity.
ACTION:
Ensure that the entity is valid, and that all necessary domain controllers are
available.
_________________
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.
Last edited by bruce2359 on Thu Feb 21, 2008 7:56 am; edited 2 times in total |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Thu Feb 21, 2008 7:47 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
no it is mq that creates the COD under the authority of the userid in the MD of the message that requested the COD. the userid of the getting application or of the trigger monitor is not relevant here.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Feb 21, 2008 7:57 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
See what happens when I type too fast for my brain? Thanks Mr. Butcher.
I've updated my post.
_________________
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 |
|
|
| Mr Butcher |
| Posted: Thu Feb 21, 2008 11:02 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
same happened to me 1 page before. 
_________________
Regards, Butcher |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
