| Author |
Message
|
| shashir |
 Posted: Mon Sep 24, 2012 10:13 am Post subject: Topic Publish Error - reason '2035' ('MQRC_NOT_AUTHORIZED') |
 |
|
Novice
Joined: 24 Sep 2012
Posts: 13
|
My JMS application throws the following exception
-------------------------------------------------------------------------------------
2CA0056I: The Connection Manager received a fatal connection error from the Resource Adapter for resource JMS$SecurityTCF$JMSManagedConnection@0. The exception is: com.ibm.msg.client.jms.DetailedJMSSecurityException: JMSWMQ2006: Failed to open MQ topic 'topic:\\com\sus\pevents\ltrack'. JMS attempted to perform an MQOPEN, but WebSphere MQ reported an error. Use the linked exception to determine the cause of this error. Check that the specified topic and queue manager are defined correctly.:com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED').
----------------------------------------------------------------------------------------
My Environment:
My JMS application is running on WAS 8.0.0.4 (WebSphere MQ Resource Adapter version 7.0.1.7-k701-107-111107)
MQ Server version 7.0.1.8
I came across a similar issue here in this forum @
http://www.mqseries.net/phpBB2/viewtopic.php?p=319403&sid=450467aeafad7a7e25cb38e17f930d04
and set the jvm property(com.ibm.mq.jms.ForceUserID=true) of my WAS Server.
I verified that after adding the above jvm property, user id is now passed.
However I still get the same exception.
Some additional information:
I checked with my MQ Server administrators for any relevant logs on MQ Server side, I got to know from them that, they see a 'CHG' request and hence might be throwing that 'un authorized' exception.
I'm able to successfully send/receive messages to a MQ Queue running on the same Queue Manager (as that of my MQ Topic).
Can anyone help me resolve this issue? I can send more information if you need.
Thank you for your help, guidance and time.
Please point me to the right forum, if this is not the relevant forum.
Thanks & Regards
Shashir
Last edited by shashir on Mon Sep 24, 2012 10:31 am; edited 2 times in total |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Sep 24, 2012 10:24 am Post subject: Re: Topic Publish Error - reason '2035' ('MQRC_NOT_AUTHORIZE |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shashir wrote: |
| I'm able to successfully send/receive messages to a MQ Queue running on the same Queue Manager (as that of my MQ Topic). |
This just proves it's not a connection issue
| shashir wrote: |
| Can anyone help me resolve this issue? |
Have you verified with the admins that you have the necessary permissions to publish to the topic you're using with the user id you're using (as suggested in the error text)?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shashir |
| Posted: Mon Sep 24, 2012 10:35 am Post subject: |
|
|
Novice
Joined: 24 Sep 2012
Posts: 13
|
Hi,
Thank you for your quick reply,
Yes, I did verify with my MQ Server admins, the user which starts my WAS server has permission(s) to publish to that MQ Topic.
But Admins say that, they see 'CHG' request on the Queue Manager when ever I publish my message to that MQ Topic. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Sep 24, 2012 10:45 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shashir wrote: |
| But Admins say that, they see 'CHG' request on the Queue Manager when ever I publish my message to that MQ Topic. |
By which they've determined that your request requires (and lacks) "chg" authority?
What topic string are you publishing to? Are you publishing /foo/bar when the topic object is /foo/*?
What WMQ object do they say "chg" is being requested against?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shashir |
| Posted: Mon Sep 24, 2012 11:09 am Post subject: |
|
|
Novice
Joined: 24 Sep 2012
Posts: 13
|
The admins enabled some kind of monitoring on the MQ Server by which they say 'CHG' is getting issued.
The 'CHG' is getting issued on the Queue Manager. This is the Queue Manager on which my topic is created.
The topic string I'm publishing to is 'com/sus/pevents/ltrack' |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Sep 24, 2012 11:33 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shashir wrote: |
| The topic string I'm publishing to is 'com/sus/pevents/ltrack' |
Is that the string you're using or the topic object on the queue manager? I find your answer ambiguous.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shashir |
| Posted: Mon Sep 24, 2012 11:36 am Post subject: |
|
|
Novice
Joined: 24 Sep 2012
Posts: 13
|
I'm sorry, if I confused you.
That is the string I'm using. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Sep 24, 2012 11:42 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shashir wrote: |
| I'm sorry, if I confused you. |
It's not hard to do
| shashir wrote: |
| That is the string I'm using. |
So what's the topic object called on the queue manager (assuming there is one)? What's the topic string on which authority has been granted?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shashir |
| Posted: Mon Sep 24, 2012 12:09 pm Post subject: |
|
|
Novice
Joined: 24 Sep 2012
Posts: 13
|
I don't know the topic object, I will provide you the answer for that tomorrow, as my MQ admins left for the day. not nice answer but that is what it is.
My earlier conversation with MQ Admins is that, I've PUT authority on the topic string 'com/sus/pevents/ltrack'.
Will confirm both the answers again with my Admins and will provide you the details. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Sep 24, 2012 12:24 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shashir wrote: |
| My earlier conversation with MQ Admins is that, I've PUT authority on the topic string 'com/sus/pevents/ltrack'. |
They might want to try giving you PUB authority to a topic rather than PUT.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shashir |
| Posted: Mon Sep 24, 2012 12:36 pm Post subject: |
|
|
Novice
Joined: 24 Sep 2012
Posts: 13
|
Sure, will check on that.
also is it possible to have a topic string with out an associated topic object?
Some background: We moved from MQ 6 to MQ 7 and I'm not sure if MQ 6 has Topic objects thing. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Sep 24, 2012 12:56 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| shashir wrote: |
| also is it possible to have a topic string with out an associated topic object? |
Yes.
| shashir wrote: |
| Some background: We moved from MQ 6 to MQ 7 and I'm not sure if MQ 6 has Topic objects thing. |
It didn't. |
|
| Back to top |
|
|
| shashir |
| Posted: Tue Sep 25, 2012 4:35 am Post subject: |
|
|
Novice
Joined: 24 Sep 2012
Posts: 13
|
Hi,
I'm still waiting on the topic object thing from my Admins.
Here is something interesting:
The same JMS application running on WAS 6.1 server is able to successfully publish messages to this MQ Topic.
WAS 6.1 server also runs with same User Id as that of my WAS 8.0.0.4 server.
This really confuses me. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Sep 25, 2012 4:48 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shashir wrote: |
| The same JMS application running on WAS 6.1 server is able to successfully publish messages to this MQ Topic |
Via the same queue manager? Or to a v6 queue manager?
| shashir wrote: |
| WAS 6.1 server also runs with same User Id as that of my WAS 8.0.0.4 server. |
Does it use the same WMQ client? 2 levels back it shouldn't be & may be using a v6 API to publish.
| shashir wrote: |
| This really confuses me. |
Then you should be pushing your admins for more help.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shashir |
| Posted: Tue Sep 25, 2012 5:21 am Post subject: |
|
|
Novice
Joined: 24 Sep 2012
Posts: 13
|
Yes via the same Queue Manager [Queue manager 7.0.1.8]
WAS 6.1 uses WebSphere MQ Resource Adapter 6.0.2.1, so its WMQ client 6.x version
WAS 8.0.0.4 uses WebSphere MQ Resource Adapter 7.0.1.7, so its WMQ client 7.x version
WAS 6.1 & WAS 8.0.0.4 uses different WMQ clients. |
|
| Back to top |
|
|
|
|
