Author |
Message
|
vincent |
Posted: Fri May 26, 2006 7:52 am Post subject: 2035 Error |
|
|
Voyager
Joined: 21 Apr 2006 Posts: 81
|
Both the MQ Server and Client is intalled on the same Solairs box.
When i complied the code with -lmqic and run, it works fine and the listener and channels are started prior to run the code and the environment uses MQSERVER to connect to the server.
But when i compiled the code with -lmqm and run, it throws me an error says that MQCONN ended with reason code 2035. It is an authorization error for MQ Manager. What could be the problem? is there any extra process to be started from MQ Server level?
The followings are running on the server box
mqm 3480 3479 0 17:44:06 ? 0:00 /opt/mqm/bin/amqzfuma -m SOPHIS
mqm 3484 3479 0 17:44:06 ? 0:00 /opt/mqm/bin/amqzdmaa -m SOPHIS
mqm 3483 3479 0 17:44:06 ? 0:00 /opt/mqm/bin/amqrrmfa -m SOPHIS -t2332800 -s2592000 -p2592000 -g5184000 -c3600
mqm 3481 3479 0 17:44:06 ? 0:35 amqhasmx SOPHIS /var/mqm
mqm 3482 3479 0 17:44:06 ? 0:02 amqzllp0 -mSOPHIS ?
mqm 3479 1 0 17:44:06 ? 0:00 amqzxma0 -m SOPHIS
mqm 3610 1 0 18:17:23 ? 2:29 /opt/mqm/bin/amqrmppa -m SOPHIS
mqm 3485 3479 0 17:44:06 ? 0:00 /opt/mqm/bin/runmqchi -m SOPHIS
mqm 3486 3479 0 17:44:06 ? 0:mqm 3651 533 0 18:33:14 pts/1 0:00 runmqlsr -t tcp -p 1417 -m SOPHIS
00 amqzlaa0 -mSOPHIS -fip0 |
|
Back to top |
|
 |
WBI_user |
Posted: Fri May 26, 2006 8:26 am Post subject: |
|
|
Partisan
Joined: 07 Aug 2001 Posts: 386
|
MQ authenticate the user who runs the program that issues the MQCONN. Please make sure that the user Id which run the MQ program is authorised to connect to the Qmgr.
You probably has to use setmqaut command to set up the proper authority for the user unless the user has mqm authority. |
|
Back to top |
|
 |
vincent |
Posted: Fri May 26, 2006 10:19 am Post subject: |
|
|
Voyager
Joined: 21 Apr 2006 Posts: 81
|
I got a sudo acces to the box to login as mqm user. Hope it should work, right. Where can i look at MQ level if i want to verify? |
|
Back to top |
|
 |
tleichen |
Posted: Fri May 26, 2006 12:31 pm Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005 Posts: 663 Location: Center of the USA
|
Look at dspmqaut.  _________________ IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
Back to top |
|
 |
mvic |
Posted: Fri May 26, 2006 12:41 pm Post subject: |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
vincent wrote: |
I got a sudo acces to the box to login as mqm user. Hope it should work, right. Where can i look at MQ level if i want to verify? |
On a general point, it is expected that mqm group is used for MQ administrators. Not for running applications. |
|
Back to top |
|
 |
vincent |
Posted: Fri May 26, 2006 1:44 pm Post subject: |
|
|
Voyager
Joined: 21 Apr 2006 Posts: 81
|
mvic,
How does the server application run if it is not linked with mqm library?you mean to say that the server application should have mqm privilege? |
|
Back to top |
|
 |
mvic |
Posted: Fri May 26, 2006 2:18 pm Post subject: |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
vincent wrote: |
How does the server application run if it is not linked with mqm library? |
A server-bound app must be linked with libmqm.so (libmqm.sl on HP-UX, libmqm.a on AIX, mqm.lib/mqm.dll on Windows...). However, I was talking about the use of the mqm group. This was because you were talking about sudo and the mqm user. Maybe I misunderstood what you were saying. But I wanted to give a reminder that the mqm group (including the mqm user) is not intended for running apps.
Quote: |
you mean to say that the server application should have mqm privilege? |
No, this is the opposite of what I think is best practice. "have mqm privilege" == "run program as an mqm group user". In my humble opinion, you should not plan to do this in production, or even in development. Users in the mqm group are MQ administrators. They are not subject to the normal authorization checks.
The reason you see 2035 errors will be because the "user your app is running under" is not authorized. Check out the discussion of setmqaut, dspmqaut etc. in the manuals.
In the past, when others have encountered 2035 failures (they are common when setting up a system for the first time) people here at mqseries.net have recommended turning on queue manager authorization events. If you do this, you should be able to review the event message(s) to find out the precise reason for the authorization failure.
Hope this helps |
|
Back to top |
|
 |
|