| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Receive 3081 on subscription request |
« View previous topic :: View next topic » |
| Author |
Message
|
| crgharm |
 Posted: Thu Oct 24, 2002 4:50 am Post subject: Receive 3081 on subscription request |
 |
|
Novice
Joined: 25 Apr 2002
Posts: 21
Location: St. Louis, Missouri
|
I have a topic called SAP/MATMAS. The principles associated with this topic is:
PublicGroupRef Publish-Deny, Subscribe-Allow, Persistence-Allow
zbb1706 Publish-Deny, Subscribe-Allow, Peristence-Allow
sapsys Publish-Allow, Subscribe-Allow, Persistence-Allow
When I send a subscription request to the SYSTEM.BROKER.CONTROL.QUEUE, with zbb1706 as the principle, I get a response back with a reason code of 3081 - MQRCCF_NOT_AUTHORIZED. You are not authorized to perform the requested action. Authorization settings for the broker are handled from the Control Center.
According to the list above I should have subscribe priveledges. The only user that has been able to successfully subscribe is the mqsiadm user.
Any idea on what I missed here?
Thanks,
Craig |
|
| Back to top |
|
 |
| jsware |
| Posted: Wed Dec 21, 2005 5:20 am Post subject: |
|
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
At the risk of upsetting some due to the age of this original post I thought I would record here what I found when I had a similar problem.
I had this response too when the PubSub broker was on a different machine than my JMS subscriber.
What I found was that if you try to register a subscription, the broker checks that the user ID you are using to register the subscription has the necessary authority to put to the subscription queue (i.e. the queue where the publications are delivered for consumption by the subscriber and not the SYSTEM.BROKER.CONTROL.QUEUE or SYSTEM.BROKER.DEFAULT.STREAM). Thus for me I had missed allowing the subscriber's user ID authority to put messages onto the xmitq from the broker qmgr to my local qmgr hosting my subscriber app.
Thus I would guess that you need to check that the subscriber application's user ID has authority to PUT messages onto the subscription queue (e.g. SYSTEM.JMS.ND.SUBSCRIBER.QUEUE or whatever you specify if you are not using JMS) even though you only expect to get messages from it. It seems that the broker attempts to put the message using your subscriber user ID as alternative authority.
HTH anybody who has also received this error, done a search and found unanswered questions.
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
| 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
|
|
|
|
