| Author |
Message
|
| Empeterson |
 Posted: Wed Feb 04, 2004 1:22 pm Post subject: Error deploying to new broker... |
 |
|
Centurion
Joined: 14 Apr 2003
Posts: 125
Location: Foxboro, MA
|
I just created a second broker on an AIX machine. When I try to deploy to that broker, I get the following error on both the broker machine and the config manager:
Feb 4 16:14:24 ufxcpidev WMQIv210[51966]: (UFXCPIBAT.default)[2057]BIP7150E: Us
er id 'db2admin' not authorized to put to queue 'SYSTEM.BROKER.ADMIN.REPLY' on q
ueue manager 'MFXMQI01' using accounting token '00000000000000000000000000000000
00000000000000000000000000000000'. : UFXCPIBAT.329ab381-fa00-0000-0080-d6797dbd1
5a3: /build/S210_P/src/DataFlowEngine/ImbPubSubSubscribeMessageHandler.cpp: 261:
ImbPubSubSubscribeMessageHandler::getAttributes: ComIbmPSControlNode: ControlNo
de
The deploy does seem to be successful, but I am getting this error anyway. Deploying to the already existing broker does not produce this error. The config mgr is running under user id db2dmin, while the brokers on AIX are running on user id wmqiadm. The db2admin id has full mq rights on the config manager box. What can be causing this problem? Why can I deploy fine to one of the brokers, but not the new one? Thank you for your help.
_________________
IBM Certified Specialist: MQSeries
IBM Certified Specalist: Websphere MQ Integrator |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Wed Feb 04, 2004 2:08 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
my guess would be your mq rights on the broker queuemanager for db2admin are not enough. you created the broker using wmqiadm and thus this userid is properly authorised.
since you have one broker on one queuemanager working fine,
lookup the group id of userid db2admin on the broker machine,
execute: amqoamd -m qmgrname -s | grep groupid of db2admin
to see which autorisations are set,
apply those definitions to the other broker queuemanager and don't forget to refresh security... 
Michael |
|
| Back to top |
|
|
| skn |
| Posted: Wed Feb 04, 2004 2:10 pm Post subject: |
|
|
Centurion
Joined: 21 May 2003
Posts: 112
Location: Dallas
|
| Do both the brokers use the same userID? |
|
| Back to top |
|
|
| Empeterson |
| Posted: Wed Feb 04, 2004 2:27 pm Post subject: |
|
|
Centurion
Joined: 14 Apr 2003
Posts: 125
Location: Foxboro, MA
|
Michael-There is no user id 'db2admin' on the broker machines. It only exists on the config manager box.
Yes, both broker use the same user id.
I got got curious and started running some tests. First, I stopped the channel from the broker queue manager to the config mgr qmgr and did a deploy. Sure enough there was a message on the xmit queue going back to the config manager. I then stopped the config manager and started the channel on the broker side back up. The message went to the SYSTEM.BROKER.ADMIN.REPLY queue with no problems. Here is the interesting part, I started the config manager back up and at that point the message dispappeares from the queue and then these errors messages popped up on both the broker machine and the config manager machine.
_________________
IBM Certified Specialist: MQSeries
IBM Certified Specalist: Websphere MQ Integrator |
|
| Back to top |
|
|
| Missam |
| Posted: Wed Feb 04, 2004 3:01 pm Post subject: |
|
|
Chevalier
Joined: 16 Oct 2003
Posts: 424
|
| Check that on configmgr box whether user db2admin was in the group mqm |
|
| Back to top |
|
|
| Empeterson |
| Posted: Wed Feb 04, 2004 3:12 pm Post subject: |
|
|
Centurion
Joined: 14 Apr 2003
Posts: 125
Location: Foxboro, MA
|
It is.
_________________
IBM Certified Specialist: MQSeries
IBM Certified Specalist: Websphere MQ Integrator |
|
| Back to top |
|
|
| Missam |
| Posted: Wed Feb 04, 2004 7:56 pm Post subject: |
|
|
Chevalier
Joined: 16 Oct 2003
Posts: 424
|
Hi
You are saying that you can see the message travelling both sides.you are right,it may be the error message generated at the broker side and send it to configmgr.if you trace the backing message sure it won't be put into configmgr queue with db2admin credentials.
as Michael said you can check the authorizations of broker1 and apply to broker2 |
|
| Back to top |
|
|
| Empeterson |
| Posted: Thu Feb 05, 2004 6:40 am Post subject: |
|
|
Centurion
Joined: 14 Apr 2003
Posts: 125
Location: Foxboro, MA
|
I changed the id the config manager runs under from db2admin to wmqiadm, and that seems to have solved the problem. We have a sand box broker running on that same machine and that runs under the wmqiadm id. I dont know why the config manager was set up to run under db2admin, nor do I have any idea why deploys would work error free on the aix broker that we have had running for well over a year now and not work for a new broker. Both the db2admin and wmqiadm id's have the exact same rights on the config manager machine.
_________________
IBM Certified Specialist: MQSeries
IBM Certified Specalist: Websphere MQ Integrator |
|
| Back to top |
|
|
|
|
