Author |
Message
|
aky201086.amit |
Posted: Thu Feb 24, 2011 6:33 pm Post subject: 2035 on Alias queue(pointing to a cluster queue) |
|
|
Newbie
Joined: 24 Feb 2011 Posts: 4
|
Hi All,
We have 2 Queue Managers QM1 and QM2. Both are in same cluster. Following queues are defined on these 2 qmgrs. app1 and app2 are 2 application ids which own their respective queues.
QM1:
REQUEST.APP2 (Alias Queue with target queue REQUEST.APP2)
REPLY.APP1(Local Clustered)
QM2:
REQUEST.APP2(Local clustered)
REPLY.APP1(Alias Queue with target queue REPLY.APP1)
Following are the permissions on the objects
QM1 and QM2: app1 -> inq and connect
app2 -> inq and connect
REQUEST.APP2(Alias on QM1): app1 -> inq and put
app2 -> inq and put
REPLY.APP1(Local clustered on QM1): app1-> inq,put,browse and get
app2-> inq and put
REQUEST.APP2(Local clustered on QM2): app1-> inq and put
app2-> inq,put,browse and get
REPLY.APP1(Alias on QM2: app1 -> inq and put
app2 -> inq and put
Job is running on QM1 by app1 id to put a request msg on REQUEST.APP2 queue on QM1 which is successfully routed to REQUEST.APP2 on QM2 but app2 got 2035 error when try to put the reply message on alias queue REPLY.APP1 on QM2.
As a workaround i gave put permission for app2 id on SCTQ on QM2 and it is working fine. can someone tell me the permanent fix for this issue as i don't want any id to access SCTQ and don't want to create any remote queue to act as QA. |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Feb 24, 2011 8:24 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Did it really try to put the reply to the alias reply to queue, or did it try to do the standard thing and put the message on a queue with standard resolution.
My guess is that the problem lies with the fact that there is no authorization for the default path to the reply to qmgr.
Welcome to the realities of request / reply...
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Feb 24, 2011 8:50 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Quote: |
REQUEST.APP2 (Alias Queue with target queue REQUEST.APP2)
REPLY.APP1(Local Clustered) |
It would help us help you if you use runmqsc to display the object definitions - then post them here - rather than what (little) you have provided. _________________ 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 |
|
 |
sandy.rajh |
Posted: Tue Mar 01, 2011 2:10 am Post subject: |
|
|
Newbie
Joined: 14 Aug 2008 Posts: 9
|
Have you provided the access to SYSTEM.CLUSTER.TRANSMIT.QUEUE for application user/group id? |
|
Back to top |
|
 |
exerk |
Posted: Tue Mar 01, 2011 2:42 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
sandy.rajh wrote: |
Have you provided the access to SYSTEM.CLUSTER.TRANSMIT.QUEUE for application user/group id? |
Try reading the last line of the original post  _________________ 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 |
|
 |
aky201086.amit |
Posted: Fri Mar 04, 2011 12:30 am Post subject: |
|
|
Newbie
Joined: 24 Feb 2011 Posts: 4
|
I have the following error logs
Error writing the reply message to queue.|MQJMS2008:failed to open MQ queue REPLY.APP1
MQException:MQJE001:completion code2, reason 2035 |
|
Back to top |
|
 |
exerk |
Posted: Fri Mar 04, 2011 12:36 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
aky201086.amit wrote: |
MQException:MQJE001:completion code2, reason 2035 |
Good. You have now identified the problem, so all you have to do is fix it. _________________ 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 |
|
 |
PeterPotkay |
Posted: Fri Mar 04, 2011 4:21 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Turn on Authority Events at the QM level. The next time the app gets a 2035, you will get an event message in SYSTEM.ADMIM.EVENT.QUEUE that will tell you exactly what ID is having trouble with what MQ API call against what MQ object.
But if you have a request / reply scenario and your app needs to be able to reply to the Reply To Queue and Reply To Queue Manager field of the request message, you are going to have to give +put access to the SYSTEM.CLUSTER.TRANSMIT.QUEUE if that queue is the way back to the Reply To Queue Manager. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
|