MQSeries.net :: View topic

pawel_janowski · Posted: Thu Feb 01, 2007 4:16 am Post subject:

Hi!
I've got a strange problem, as follows:
1) I've created broker called DBRK1 and registered it in cfgmgr
2) I've tried to remove it, but it was not successful I suppose, because when I try to register again broker with the same name I obtain the message:

"BIP1506E: Queue manager 'DMQBRK1' cannot be associated with broker 'DBRK1'; it may still be in use by another broker 'DBRK1' which is pending deletion.

Broker 'DBRK1' has been removed from the domain of active brokers, although it may still be using its queue manager. It is not possible to associate another broker with the queue manager until the Configuration Manager can confirm that the first broker has tidied up its resources.

After successfully removing a broker from the domain, you must initiate a deploy of the topology in order to instruct the broker component to stop and tidy up its resources. This can be done using the Message Brokers Toolkit, mqsideploy utility or the Configuration Manager Proxy API. Once the deploy is successful, you must delete the broker component using the mqsideletebroker command. Only then can you associate a new broker with the queue manager.
If the runtime broker component has already been deleted and is therefore unable to cleanly tidy up its resources, you must purge any remaining references to the broker and its queue manager from the Configuration Manager's repository. To do this, either (a) make the queue manager or its SYSTEM.BROKER.ADMIN.QUEUE inaccessible to the Configuration Manager and initiate a topology deploy, or (b) use the Configuration Manager Proxy API TopologyProxy.removeDeletedBroker().
____________________________________________________________
BIP1712W: Broker not found

An attempt was made to view or modify the Broker with UUID '64a5037d-1001-0000-0080-9d448a633d49', but it does not exist in the Configuration Manager's repository.

If you are trying to manipulate an object immediately after submitting a request to create it, it is likely that there was a problem creating the object. An example of this is if you attempt to create a default execution group without first ensuring that the parent broker was created successfully; this error suggests that there was a problem creating the broker.
Check the Configuration Manager's logs to see why the Broker could not be found. If the object has previously been available, the receipt of this error may indicate corruption in the Configuration Manager's repository; if this is the case, you may need to use mqsirestoreconfigmgr to restore the Configuration Manager's repository, or if this is not possible, contact your IBM support center for advice.
____________________________________________________________
BIP1712W: Broker not found

An attempt was made to view or modify the Broker with UUID '64a5037d-1001-0000-0080-9d448a633d49', but it does not exist in the Configuration Manager's repository.

If you are trying to manipulate an object immediately after submitting a request to create it, it is likely that there was a problem creating the object. An example of this is if you attempt to create a default execution group without first ensuring that the parent broker was created successfully; this error suggests that there was a problem creating the broker.
Check the Configuration Manager's logs to see why the Broker could not be found. If the object has previously been available, the receipt of this error may indicate corruption in the Configuration Manager's repository; if this is the case, you may need to use mqsirestoreconfigmgr to restore the Configuration Manager's repository, or if this is not possible, contact your IBM support center for advice.
____________________________________________________________
BIP1510E: Deployment failed; a deployment is already in progress to broker DBRK1

The Configuration Manager was asked to deploy to broker DBRK1, but this could not be attempted because it has not yet received a response to a previous deployment request submitted to that broker. To ensure that the deployed configuration is consistent with the reported configuration, the more recent deployment request has been discarded.
Note that if you are attempting to deploy the publish/subscribe topology or topic hierarchy, no brokers in the domain will have received the new deployment message. There can be no outstanding deploys in the domain before deployment of such a configuration can occur.

Wait for the outstanding deploy to complete before retrying the operation. The Event Log Editor or Configuration Manager Proxy may be used to check that all responses to the outstanding deploy have been received and processed. If the outstanding deploy does not fully complete in a suitable period of time, check that all brokers exist and are running, all WebSphere MQ queue managers are running, and that all channels between queue managers are started. Also check that deploy messages have been correctly delivered to the target brokers, and have not been put to the dead letter queue. Correct any problems you find. If it still does not complete, then cancel the deploy operation; either (a) right-click the broker in the Message Brokers Toolkit and select the 'Cancel Deployment' option, or (b) use mqsideploy with the -c option, or (c) use the BrokerProxy.cancelDeployment() method in a Configuration Manager Proxy application. Note that cancelling the deployment operation does not stop the deployment message from being processed by the broker; it simply forces the Configuration Manager to remove any outstanding deployment locks that may be associated with the broker. If a broker subsequently processes a deployment message that has been cancelled using this technique, the deployed configuration may become inconsistent with the reported configuration."

So it seems that there is a previous broker registered somewhere in my configmgr.

Well, in such situation I've decided to remove CfgMgr and its queue manager as well.

Then I've recreated the queue manager and then created configmgr on that QM. And ... it still can see the previous broker and does not allow to register a new one (with the same message as above).

Can anyone help me? Where that cfgmgr stored the information about the previous broker?

Pawel J
_________________
Pawel Janowski