BIP1506

Severity

20 : Error

Message

Queue manager '<insert_2>' cannot be associated with broker '<insert_0>'; it may still be in use by another broker '<insert_1>' which is pending deletion.

Explanation

Broker '<insert_1>' 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.

Response

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().