| Author |
Message
|
| sksharma |
 Posted: Fri Apr 25, 2008 3:33 am Post subject: Getting error while creating message broker, |
 |
|
Apprentice
Joined: 18 Apr 2008
Posts: 28
|
"BIP2045E: Broker WBRK_BROKER running on WebSphere queue manager WBRKCM_QM did not process a deployment message, because it was addressed to a broker with a different identifier."
Allthough i followed the process given below which was there in the eventlog still getting the same error
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 b7e06a84-1901-0000-0080-a142ab7c7af3, but this does not match the UUID of the running broker (5c2c6084-1901-0000-0080-a142ab7c7af3).
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 WBRK_BROKER to 5c2c6084-1901-0000-0080-a142ab7c7af3. This will allow the Configuration Manager to deploy to the broker, although any resources previously deployed to the broker will not be monitored by the Configuration Manager (unless they were already being monitored by that Configuration Manager).
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"
kindly let me know how i can fix this issue
thanks in advance
wth rgrds
Sksharma |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Apr 25, 2008 3:39 am Post subject: Re: Getting error while creating message broker, |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| sksharma wrote: |
| 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. |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| broker_new |
| Posted: Fri Apr 25, 2008 3:57 am Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
Sharma are u able to resolve the issue because for me its not working.
Deleting the Broker and recreating the broker with the same name did not resolve the issue.I deleted both broker and config manager then i added broker to configuration manager using toolkit.it is able to deploy message flows.
_________________
IBM ->Let's build a smarter planet |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Apr 25, 2008 4:03 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you do not follow these steps carefully, completely, and in the right order... then yes you will have to delete the configmgr as well.
Or use the CMP API Excerciser to clean things up.
Or in v6.1 you can adopt the broker.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| broker_new |
| Posted: Fri Apr 25, 2008 4:06 am Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
I do know why configuration manager still keeps the UUID values in repository once broker is deleted.Because if again if we create the broker with the same name it tells it expects this UUID but the running broker has some other UUID
_________________
IBM ->Let's build a smarter planet |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Apr 25, 2008 4:15 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| broker_new wrote: |
| I do know why configuration manager still keeps the UUID values in repository once broker is deleted.Because if again if we create the broker with the same name it tells it expects this UUID but the running broker has some other UUID |
It doesn't keep them.. if you follow the steps in the correct order.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| sri_csee1983 |
| Posted: Sun Apr 27, 2008 6:46 pm Post subject: |
|
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
Dear Friends,
I got this problem in MB5. I was able to overcome the with the same procedure with one extra step. In the CM DB, Just check for the corresponding broker entry in the table cbroker. The field name is cname. If any entry is there in tht table just delete and retry. Try to do this step after u finish mqsideletebroker in the below steps mentioned by u people and then use mqsicreatebroker. Hope this may work  May be u can also check for the UUID in the same table. The field for the UUID is CUUID.
_________________
With Cheers,
Sri |
|
| Back to top |
|
|
|
|
