MQSeries.net :: View topic

vikyonly · Posted: Tue Apr 24, 2007 7:57 am Post subject: BIP7150E

Hi,

Need help in sorting out following error.

Before I provide logs let me give you a little background.

My Configuration manager is on Windows 2000, and Broker on Solaris 8.

When ever I deploy a *.bar file, it does get deployed on broker but I do get following error in Event logs.

ToolKit -
BIP1536S: Configuration Manager unable to register for internal subscriptions with broker XXBROKER_B.

Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker

XXBROKER_B was not successful. This means that the Message Brokers Toolkit may not reliably show the correct status of the resources assigned to broker

XXBROKER_B. The Configuration Manager also writes this message to the system event log, accompanied by other messages giving details of the problem.

Look at the messages for this problem in the system event log. Determine and correct the cause of the problem before attempting to deploy to this broker

again. If this problem persists, contact your IBM support center.

Followings is what i got from event logs.

Event log -
1.
( ConfigMgr ) User id 'ABCD6148' not authorized to put to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'CFMR1T' using accounting token

'0000000000000000000000000000000000000000000000000000000000000000'.

The user is not authorized to put a message on the named queue.

Ensure the user is allowed to perform this operation. This may involve configuring the WebSphere Business Integration settings for this queue, or using an

alternative userid which is authorized.

2.
( ConfigMgr ) Error detected whilst processing a message in node 'DynamicSubscriptionEngine'.

The message broker detected an error whilst processing a message in node 'DynamicSubscriptionEngine'. An exception has been thrown to cut short the

processing of the message.

See the following messages for details of the error.

3.
( ConfigMgr ) Invalid configuration message. See the following messages for details of the error.

The publish/subscribe function of the broker has received an invalid configuration message and has not updated its configuration. This can arise as a result

of errors in the specification of the broker topology or topics which the Configuration Manager was unable to detect. It can also result from the broker

having become out of step with the configuration repository or from other applications sending extraneous messages to the configuration queues of the broker

(SYSTEM.BROKER.ADMIN.QUEUE and SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).

Check the relevant topology and topic definitions, perform a complete redeploy of the configuration and ensure that no applications are writing to the

configuration queues.

4.
( ConfigMgr ) Broker XXBROKER_B could only process parts of the internal configuration message.

Parts of the internal configuration message were not processed successfully.

This response indicates that one or more Execution Groups could not process the internal configuration message. Analyze all of the following messages to

determine why the internal configuration message could not be processed.

5.
ConfigMgr ) Configuration Manager unable to register for internal subscriptions with broker XXBROKER_B.

Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker

XXBROKER_B was not successful. This means that the Message Brokers Toolkit may not reliably show the correct status of the resources assigned to broker

XXBROKER_B. The Configuration Manager also writes this message to the system event log, accompanied by other messages giving details of the problem.

Look at the messages for this problem in the system event log. Determine and correct the cause of the problem before attempting to deploy to this broker

again. If this problem persists, contact your IBM support center.

Initially I thought its because of id 'ABCD6148' not included in mqm & mqbrkrs groups. But this user id do exists in both groups. And following test show that user 'ABCD1648' do have right permissions.

Command Link -
C:\Documents and Settings\AdminXXY>dspmqaut -m CFMR1T -t q -n SYSTEM.BROKER.ADMIN.REPLY -p ABCD6148

Entity ABCD6148 has the following authorizations for object SYSTEM.BROKER.ADMIN.
REPLY:
get
browse
put
inq
set
crt
dlt
chg
dsp
passid
passall
setid
setall
clr

Following is error from Broker,
Broker Machine -
Apr 24 16:10:09 xxxx8043 MQSIv500[5800]: [ID 702911 user.error] (XXXXKR1T_B.TEST_EXECGROUP)[27]BIP7150E: User id 'ABCD6148' not authorized to put to queue

'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'CFMR1T' using accounting token '0000000000000000000000000000000000000000000000000000000000000000'. :

XXXXKR1T_B.d50a658e-1101-0000-0080-9f52b6221e01: /build/S500_P/src/DataFlowEngine/JavaNodeLibrary/ImbPubSubSubscribeMessageHandler.cpp: 524:

ImbPubSubSubscribeMessageHandler::checkQueueAuthority: ComIbmPSControlNode: ControlNode

Am still very puzzeled why its still throuwing this error. Any clues to get this resolved will be great help.

Thank you.

Regards