| Author |
Message
|
| Rama |
 Posted: Fri Jun 20, 2008 2:37 am Post subject: Error occured while deploying flow on to execution group |
 |
|
Newbie
Joined: 24 Mar 2008
Posts: 3
|
Hi All,
Platform - windows XP, MB 6.0
Error occured while deploying flow on to execution group , please check the error below:
BIP2045E: Broker WBRK6_DEFAULT_BROKER running on WebSphere queue manager WBRK6_DEFAULT_QUEUE_MANAGER did not process a deployment message, because it was addressed to a broker with a different identifier.
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 94d480a5-1a01-0000-0080-f72093ce36bf, but this does not match the UUID of the running broker (ee5e78a5-1a01-0000-0080-f72093ce36bf).
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 WBRK6_DEFAULT_BROKER to ee5e78a5-1a01-0000-0080-f72093ce36bf. 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, delete the broker component, its configuration tables and its queue manager. Then remove the broker definition from the domain using the Message Brokers Toolkit or Configuration Manager Proxy, and (if using publish/subscribe) redeploy the topology. Once successful, recreate the broker component and add a reference to it using the Message Brokers Toolkit or Configuration Manager Proxy, and redeploy any resources to it.
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.
Please let me know what needed to be done.
Thanks in advance,
Ram |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Fri Jun 20, 2008 3:02 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
i suspect you messed the broker.
search in this forum,
use configuration mgr proxy to resolve this issue.
its mentioned in the error details.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| broker_new |
| Posted: Fri Jun 20, 2008 3:43 am Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
The Steps you need to follow are:
1) Delete the Broker reference from Configuration manager(While deleting let the Broker running).
2) Delete the Broker using mqsideletebroker -w option.
3) Create the Broker and start it.
4) try to add it to configuration manager and deploy the bar file.
still if you get the same problem.
Follow this
1) Delete the Broker reference from Configuration manager(While deleting let the Broker running).
2)2) Delete the Broker using mqsideletebroker -w option.
3)Go to Configruration Manager Proxy and remove the references for the deleted Broker and try creating the broker and start it and add it to cfgmgr at any cost it should work now.....
_________________
IBM ->Let's build a smarter planet |
|
| Back to top |
|
|
| broker_new |
| Posted: Fri Jun 20, 2008 3:45 am Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
It is certainly a mess as Gayathri said,because this problem arises when you delete the broker and create the broker with the same name and adding it to cfgmgr.If you are not following the steps while deleting you get this type of problems
_________________
IBM ->Let's build a smarter planet |
|
| Back to top |
|
|
| mqmatt |
| Posted: Fri Jun 20, 2008 4:49 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| broker_new wrote: |
The Steps you need to follow are:
1) Delete the Broker reference from Configuration manager(While deleting let the Broker running).
2) Delete the Broker using mqsideletebroker -w option.
3) Create the Broker and start it.
4) try to add it to configuration manager and deploy the bar file.
still if you get the same problem.
Follow this
1) Delete the Broker reference from Configuration manager(While deleting let the Broker running).
2)2) Delete the Broker using mqsideletebroker -w option.
3)Go to Configruration Manager Proxy and remove the references for the deleted Broker and try creating the broker and start it and add it to cfgmgr at any cost it should work now..... |
...or read the user response section of the error message.  |
|
| Back to top |
|
|
| sri_csee1983 |
| Posted: Fri Jun 20, 2008 5:03 am Post subject: |
|
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
Hey Or if u r playing with ur development environment just make this try. Its simple and will work
Just check in the config mgr db in the table cbroker, issue the following command
select CNAME,CUUID from CBROKER where CNAME='WBRK6_DEFAULT_BROKER'
U ell get the old value of cuuid thts either of the two that is listed in ur error. The one which is not in the table is the new value of cuuid then update that field with the new value (ie) use the following SQL
update cbroker set cuuid='new value' where cname='WBRK6_DEFAULT_BROKER' and then try deploying it.
It may work. It worked once for me.
_________________
With Cheers,
Sri |
|
| Back to top |
|
|
| mqmatt |
| Posted: Fri Jun 20, 2008 6:35 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
sri_csee1983,
As I said to you before, this is not good advice.
There are supported ways of solving the problem. Messing around with internal data structures is not one of them.
Regards
-Matt |
|
| Back to top |
|
|
| sri_csee1983 |
| Posted: Fri Jun 20, 2008 7:05 am Post subject: |
|
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
mqmatt,
U may be right, Thats y I told if it is a development environment he can make a try. I made this working in my development environment. What will be the worst effect? deleting and recreating the configmgr itself. Thts why asked him to make a try. But I am sure it worked for me. I too recommend this not try in a Production environment 
_________________
With Cheers,
Sri |
|
| Back to top |
|
|
|
|
