BIP2045

Severity

20 : Error

Message

Broker <insert_0> running on WebSphere queue manager <insert_2> did not process a deployment message, because it was addressed to a broker with a different identifier.

Explanation

This message usually means that an attempt has been made to assign the broker to a second (or a reinitialized) Configuration Manager.
Each broker is identified by a universally unique identifier (UUID) which is allocated when the Message Brokers Toolkit or Configuration Manager Proxy creates a definition for the broker. When deployment occurs, a UUID check is made to help prevent accidental deployment of changes to brokers not under the control of the Configuration Manager. In this case, the deployment message was addressed to a broker with a UUID <insert_3>, but this does not match the UUID of the running broker (<insert_1>).

Response

If possible, re-issue the deployment request using the Configuration Manager that administers this broker. If this is not possible, use the Configuration Manager Proxy API BrokerProxy.setUUID() method to set the UUID of broker <insert_0> to <insert_1>. This will allow the Configuration Manager to deploy to the broker, although you must then issue Remove Deployed Children for that broker, recreate your execution groups and redeploy your applications to restore a working configuration.
If all else fails, complete the following tasks in order: (1) stop and delete the broker component using mqsideletebroker, (2) remove the broker definition from the domain using the Message Brokers Toolkit or Configuration Manager Proxy, (3) recreate the broker component using mqsicreatebroker, (4) add the broker definition to the domain using the Message Brokers Toolkit or Configuration Manager Proxy (5) redeploy your message flows and related artefacts to the broker. Note the order of tasks (1) and (2), which is the reverse of the usual order of operations when deleting brokers.
To prevent this problem from recurring when deleting or recreating brokers, always remove the broker definition from the domain BEFORE the running broker component is stopped and deleted. See the WebSphere Message Brokers online documentation section "Recovering after failure" for more information.