| Author |
Message
|
| humanRebody |
 Posted: Wed Jan 12, 2011 7:01 am Post subject: WMB Toolkit cannot make a connection to WMB. |
 |
|
Novice
Joined: 05 Feb 2010
Posts: 15
|
Hi everyone,
I have installed the WMQ V7 & WMB V7 in the RHEL 5.5 64bits machine. Now I would like to connect the WMB Toolkit which is installed in Windows 7 to the WMQ but no luck.
What I have done are listed below:
1) Start the MQ Manager
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[mqm@localhost ~]$ dspmq
QMNAME(mqbroker) STATUS(Running)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2) Start the listener
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
dis lsstatus(TCP.MQBROKER7.LISTENER)
2 : dis lsstatus(TCP.MQBROKER7.LISTENER)
AMQ8631: Display listener status details.
LISTENER(TCP.MQBROKER7.LISTENER) STATUS(RUNNING)
PID(3641) STARTDA(2011-01-12)
STARTTI(21.22.53) DESCR( )
TRPTYPE(TCP) CONTROL(QMGR)
IPADDR(*) PORT(1420)
BACKLOG(100)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3) Set authority to the toolkit user
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[mqm@localhost ~]$ dspmqaut -m mqbroker -t qmgr -p Thomas
Entity Thomas has the following authorizations for object mqbroker:
connect
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
4) Start the broker
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[mqm@localhost bin]$ mqsistart broker7
BIP8018E: Component running.
This component is running, the command issued cannot be run against a running component.
Stop the component and reissue the command.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The error shown:
The user 'Thomas' is not authorized to connect to queue manager 'mqbroker' (MQ reason code 2035 while trying to connect)
Check that,
1. The broker is running.
2. The TCP/IP port of the queue manager is active if it is remote.
I was sitting for the issue for 3 nights. Could anyone give me a hand. Million Thanks. 
Regards,
Thomas |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Jan 12, 2011 7:04 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You don't use -p on Unix when issuing setmqaut.
You must use -g. |
|
| Back to top |
|
|
| humanRebody |
| Posted: Wed Jan 12, 2011 7:17 am Post subject: |
|
|
Novice
Joined: 05 Feb 2010
Posts: 15
|
| Thanks for the opinion and I have already added the user to the mqm group for problem troubleshooting. However, it still not work. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jan 12, 2011 7:20 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jan 12, 2011 9:36 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| humanRebody wrote: |
| Thanks for the opinion and I have already added the user to the mqm group for problem troubleshooting. However, it still not work. |
Did you log out and log back in, do a refresh security on MQ or bounce the qmgr since? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| eugen |
| Posted: Wed Jan 12, 2011 11:25 pm Post subject: |
|
|
Novice
Joined: 28 Dec 2010
Posts: 22
|
Had the same problem on CentOS 5.5 a while ago, I do not know if it will work for you but give it a try.
1. First log out and log in back. If this does not work - may be reboot RHEL box.
2. Try to issue this command (although I see that you already have the connect permission...) but just in case
mqsicreateaclentry <configmqrname> -u <user> -a -x F -p
I am not sure if it will help - but you can at least try.
Thx,
Eugene. |
|
| Back to top |
|
|
|
|
