BIP2045
Severity
20 : Error
Message
Broker <insert_0> (UUID <insert_1>) running on WebSphere Business Integration queue manager <insert_2> could not process an internal configuration message because the broker identity received in the message (UUID <insert_3>) did not match that of this broker.
Explanation
An internal configuration message could not be processed and was rejected. Each broker is identified by a universally unique identifier called a UUID which is allocated when the user creates a definition for the broker. The configuration message received contained a broker UUID (<insert_3>) that does not match the UUID of broker <insert_0> running on WebSphere Business Integration queue manager <insert_2>. There are two possible reasons for this. Either a user has accidentally specified queue manager <insert_2> when defining another broker so that messages destined for the other broker have arrived at this broker, or the definition for broker <insert_0> was deleted and recreated on the Message Brokers Toolkit which has the effect of giving broker <insert_0> a new, different UUID.
Response
If the queue manager name specified in the Message Brokers Toolkit was incorrect then use the Message Brokers Toolkit to correct the broker definition in error. The mqsilist command may be used to display broker queue manager names. Otherwise, if the broker definition was deleted and recreated, you must use the mqsideletebroker and mqsicreatebroker commands to recreate the broker, then redeploy the configuration for the broker in order to re-establish the correct broker identity. To avoid loss of data when recreating the broker, make sure that you follow the sequence of actions defined in the WebSphere Business Integration Message Brokers online documentation section "Recovery and restart".