Author |
Message
|
dev135 |
Posted: Thu Jan 31, 2013 12:08 pm Post subject: access to subscription queue required? |
|
|
Apprentice
Joined: 21 Oct 2008 Posts: 44
|
Hi,
I have an APP A , connecting to our QMgr(A) thru MQ client and publishes the message to a topic "A/B/C " defined on A . Now i have a subscription object defined on same qmgr A with above as Topic and Dest to a clustered queue on other queue manager(B).
APP A uses "a" as user id and when it publishes it failes to DLQ on the qmgr A. when looked the DLQ it says not able to put msg to the dest queue with 2035 error. but "a" user has pub access to topic.
so to fix it i created an alias on qmgr A to point to cluster queue on B and gave access to "a" user .
question is why we need to give access to the queue here as giving access to topic would suffice right? and moreover pub sub concept is to decouple both publsiher and subscriber..
MQ version : 7.0.1.8 (Linux on Z-series)
Thanks. |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Jan 31, 2013 1:42 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Copy/paste the complete DLH (Dead Letter Header) 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 |
|
 |
mqjeff |
Posted: Thu Jan 31, 2013 1:55 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Can you post the definition of the subscription object?
I mean did you specify just the destination name, or did you also specify a destination queue manager? |
|
Back to top |
|
 |
dev135 |
Posted: Thu Jan 31, 2013 3:55 pm Post subject: |
|
|
Apprentice
Joined: 21 Oct 2008 Posts: 44
|
As of now i dont have the DLQ messages as i cleared out once i fixed the issue. but i am sure the header conatins 2035 with destination queue name when i browsed thru rhfutil. moreover if APP A doesnt have access to topic ..the message shouldnt reach to my queue manager and would have failed at APP A side itself with NOT_AUTHORIZED error right??
@bruce : are you looking for anything specific in the DLQ header ?
below are the defintions:
DEFINE TOPIC(A.B.C) +
TOPICSTR('A/B/C') +
DESCR('TOPIC FOR APP A') DURSUB(YES)
DEFINE SUB(A.B.C.SUB) +
TOPICOBJ(A.B.C) +
DEST(test.queue) REPLACE
- no qmgr name in sub defintion.
rest of the parameters in above defintions are default
where as test.queue is dest queue. |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Feb 01, 2013 3:55 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
is the name of the queue really test.queue, or is it TEST.QUEUE or did you just forget to put it in 'test.queue' quotes when you pasted the MQSC here? |
|
Back to top |
|
 |
exerk |
Posted: Fri Feb 01, 2013 4:05 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
mqjeff wrote: |
is the name of the queue really test.queue, or is it TEST.QUEUE or did you just forget to put it in 'test.queue' quotes when you pasted the MQSC here? |
Would that not more likely give 'UNKNOWN OBJECT'? _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Feb 01, 2013 4:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
exerk wrote: |
mqjeff wrote: |
is the name of the queue really test.queue, or is it TEST.QUEUE or did you just forget to put it in 'test.queue' quotes when you pasted the MQSC here? |
Would that not more likely give 'UNKNOWN OBJECT'? |
Yes. unless there's a local 'test.queue' on the qmgr that is different than the remote TEST.QUEUE, and the user doesn't have permissions to that queue.
Don't remember how permissions on the xmitq apply here - in this case the system.cluster.transmit.queue or whatever xmitq is set for the cluster channel. |
|
Back to top |
|
 |
dev135 |
Posted: Fri Feb 01, 2013 6:23 am Post subject: |
|
|
Apprentice
Joined: 21 Oct 2008 Posts: 44
|
Sorry..its TEST.QUEUE only.
But my question is why we need to give access to the queue here or am i missing something here in my setup ? as per pub sub ..both publisher and subscriber are decopuled and who ever having access to publish doesnt really need to have the subscription queue permission to work right ?
and yes to avoid SCTQ permission i created an object on QMgr A and gave permissions to the alias . |
|
Back to top |
|
 |
dev135 |
Posted: Thu Feb 14, 2013 4:39 pm Post subject: <solved>access to subscription queue required |
|
|
Apprentice
Joined: 21 Oct 2008 Posts: 44
|
|
Back to top |
|
 |
|