| Author |
Message
|
| neocruz |
 Posted: Fri Jul 09, 2004 12:06 pm Post subject: 2035 not showing up in AMQERR01.LOG on Solaris |
 |
|
Acolyte
Joined: 13 Jun 2004
Posts: 54
|
| I've tried to connect to a queue using a 5.3 client and received a 2035. That is fine. On Solaris 9i, I've looked at that Qmgr's (5.3) error logs to see what UserID was being used. Authorev has been enabled. There's nothing in the log. I tried 5 additional times. Still nothing. Can anyone help. |
|
| Back to top |
|
 |
| kirani |
| Posted: Fri Jul 09, 2004 12:44 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
2035 means MQRC_NOT_AUTHORIZED. Please make sure the user-id has appropriate authorizations on the queue manager.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| EddieA |
| Posted: Fri Jul 09, 2004 1:12 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Turning on authorev makes MQ write a message to SYSTEM.ADMIN.QMGR.EVENT queue whenever a 2035 is generated. That message is not plain text, but you should be able to browse it and see the text parts. That would inlcude the userID that make the event. If there's also a queue name, then it's probably permissions on the queue that are wrong. If no queue name, then it's probably the connection to MQ that failed. You could look in the Event Monitoring manual if you really want to understand the message.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| neocruz |
| Posted: Mon Jul 12, 2004 7:12 am Post subject: |
|
|
Acolyte
Joined: 13 Jun 2004
Posts: 54
|
Thanks for the replies. I guess I wasn't clear. I knew the connect would fail. In Windows, those 2035 events are written to the Qmgr's error logs. An entry will say " User XXX could not connect due to ....." . This is not showing up in the Solaris Qmgr specific logs. Does anyone know why? Other events are showing up.
Rich |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Jul 12, 2004 7:43 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
You should look in the following directories on UNIX platforms
/var/mqm/qmgrs/<QMGRNAME>/errors
/var/mqm/qmgrs/@SYSTEM/errors
/var/mqm/errors |
|
| Back to top |
|
|
| neocruz |
| Posted: Wed Jul 21, 2004 12:53 pm Post subject: |
|
|
Acolyte
Joined: 13 Jun 2004
Posts: 54
|
| I've looked at all the listed directories and can't find where the Qmgr has logged a msg saying a user is not authorized to access an object. Any other ideas anyone? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jul 21, 2004 2:47 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Although I too have occasionally seen 2035 errors in the error logs (always on Windows as well), I don't rely on that. It is not documented anywhere that 2035 errors get written to the error logs, or under what conditions/platforms.
It IS documented that if you turn on Authority Events for the QM, you will see an Event anytime an app does something they are not authorized to.
To me this makes sense. If the app gets a 2035 error, they have been synchronously told the fact. Why log it in the QM's error log? You wouldn't expect to find a 2033 error in your log every time an app failed to find a message in the queue, right?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| neocruz |
| Posted: Tue Jul 27, 2004 8:20 am Post subject: |
|
|
Acolyte
Joined: 13 Jun 2004
Posts: 54
|
| I appreciate your reply. When working with my Windows Qmgrs, this is logged all the time. I use it when developers don't know what ID is being used to run the process. There are other ways to find this out but looking in the error logs is the easiest. I'll probably put this dog to bed. Thanks. |
|
| Back to top |
|
|
|
|
