| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQJMS2013, client can not connec to MQ queue manager |
« View previous topic :: View next topic » |
| Author |
Message
|
| jeevan |
 Posted: Sun Sep 13, 2009 3:25 pm Post subject: MQJMS2013, client can not connec to MQ queue manager |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
One of our Tibco application is getting the following error while connectin to a qmgr. Even it gives the same error when the user is added to the 'mqm' group. So, I thought it is not mq side of problem but my app folk think their side is ok. The app guy takes the highlited point and thinks this is an MQ issue.
JMS exception: com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2035MQJE036: Queue manager rejected connection attempt at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:212) at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:318)
I tried to browse a bit this forum, but not much success and also I am not sure what exactly causes this problem. I woud appreciate any help,
thanks
mq 5.3.11 ( we are migrating soon)
os win
cleint Tibco
They use binding file( Tibco can connect using binding file or adapter)
Last edited by jeevan on Tue Sep 22, 2009 10:22 pm; edited 4 times in total |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Sun Sep 13, 2009 4:01 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Since its Windows the details of the 2035 will be in the QM's error log.
(And please don't put urgent in the title. Why do people do that? Do they think we will all drop what we are doing as our mqseries.net pagers go off?)
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jeevan |
| Posted: Sun Sep 13, 2009 4:38 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| PeterPotkay wrote: |
Since its Windows the details of the 2035 will be in the QM's error log.
(And please don't put urgent in the title. Why do people do that? Do they think we will all drop what we are doing as our mqseries.net pagers go off?) |
Peter,
I have authorised user for connection and put/get message. Even I added that user in mqm and admin group. Even we tried with mqm. But does not work.
There is no error log in mq error log. This is an error in the client side Client is the Tibco. In the test, they use username ( not password) in connection factory, and it worked. but in production, it is not woking
Sorry for putting urgent, in fact it is. at 9 pm pdt is the go live and it isnot working, therefore i put that. Sorry abou that. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Mon Sep 14, 2009 12:25 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
You can turn on MQ authorisation events to see which object is missing the required permissions by the user.
You can then set the permissions as needed |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Sep 14, 2009 2:46 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You need authorities to the queue manager.
You need authorities to queues.
For JMS you likely need +inq.
You can not have done everything that is necessary to set the user to mqm.
In particular, if the qmgr is running on Windows, then there is no "mqm" user, just "MUSR_MQADMIN".
In particular, if you added the user to the Windows mqm group, you would have needed to issue REFRESH SECURITY in runmqsc. |
|
| Back to top |
|
|
| jeevan |
| Posted: Mon Sep 14, 2009 3:21 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| mqjeff wrote: |
You need authorities to the queue manager.
You need authorities to queues.
For JMS you likely need +inq.
You can not have done everything that is necessary to set the user to mqm.
In particular, if the qmgr is running on Windows, then there is no "mqm" user, just "MUSR_MQADMIN".
In particular, if you added the user to the Windows mqm group, you would have needed to issue REFRESH SECURITY in runmqsc. |
I did whatever it requires to authorise for a client to connect to a queue manager, put/get message inclusing browse, inq including setal.
I mean not 'mqm' but I used my id, which is used for administering the whole mq network, I used another id which is in mqm and admin group as I have mentioned in my first post but invein. The interesting thing is, it is working on TEST.
Also, there is no any 2035 or any error log in queue manager. The above error is taken from client error log. Client is Tibco which connects to MQ as jms client.
Thanks a lot
Last edited by jeevan on Tue Sep 15, 2009 9:11 am; edited 1 time in total |
|
| Back to top |
|
|
| jeevan |
| Posted: Tue Sep 15, 2009 9:04 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| jeevan wrote: |
| mqjeff wrote: |
You need authorities to the queue manager.
You need authorities to queues.
For JMS you likely need +inq.
You can not have done everything that is necessary to set the user to mqm.
In particular, if the qmgr is running on Windows, then there is no "mqm" user, just "MUSR_MQADMIN".
In particular, if you added the user to the Windows mqm group, you would have needed to issue REFRESH SECURITY in runmqsc. |
I did whatever it requires to authorise for a client to connect to a queue manager, put/get message inclusing browse, inq including setal.
I mean not 'mqm' but I used my id, which is used for administering the whole mq network, I used another id which is in mqm and admin group as I have mentioned in my first post but invein. The interesting thing is, it is working on TEST.
Also, there is no any 2035 or any error log in queue manager. The above error is taken from client error log. Client is Tibco which connects to MQ as jms client.
I will do more reserach and post tomorrow. I am travelling today.
Thanks a lot |
It was app folks problem. The Tibco went to connect to MQ with the user id it is running under, not the user id they have supplied while creating connection factory.
I asked that on Sunday too, but they could not tell me. When I dig down today, we figure out that the process is running under that user id.
When the user Tibco was running under was authorised, Tibco was able to make a connection. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
