| Author |
Message
|
| alagarsamy |
 Posted: Wed Sep 03, 2008 1:38 am Post subject: BIP1037S: Broker not found. |
 |
|
Newbie
Joined: 03 Sep 2008
Posts: 5
|
Hi
The mqsilist command shows the Broker. Configuration manager and the Queue Manager were up and running.
But when I try to create execution group,I got the below error
BIP1044I: Connecting to the Configuration Manager's queue manager...
BIP1045I: Connecting to the Configuration Manager...
BIP1037S: Broker not found.
Broker '*.*.*' was not found in the Configuration Manager repository.
Reissue the command specifying an existing broker.
Can anyone suggest what might have gone wrong here..
Regards,
Suresh |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Wed Sep 03, 2008 3:05 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
what happens if you issue mqsilist
do you have the access privileges to do so.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| alagarsamy |
| Posted: Wed Sep 03, 2008 3:16 am Post subject: |
|
|
Newbie
Joined: 03 Sep 2008
Posts: 5
|
The mqsilist showed the brokers and config managers list.
I have the access and its part of mqm group.
Now I have created the broker with the same name as listed in mqsilist via toolkit and a sample EG as well. But when I deploy the bar files,it's not getting reflected under that EG and hence in the mqsilist.
Any clues?.
Thanks,
Suresh |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Wed Sep 03, 2008 3:20 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
1. check the event logs and make sure that there are no errors logged.
2. user has to be the part of mqbrkrs.
3. whats the broker and toolkit version
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| alagarsamy |
| Posted: Wed Sep 03, 2008 3:30 am Post subject: |
|
|
Newbie
Joined: 03 Sep 2008
Posts: 5
|
Hi
I am connecting to MB 6.0.0.7 using toolkit 6.0.2 version.
Yes the user is part of mqbrkrs.
Event log:
BIP2045E: Broker BT.BK.CBS962T4 running on WebSphere queue manager BT.QM.CBS962T4 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 8737d427-1c01-0000-0080-cbb3e354bb41, but this does not match the UUID of the running broker (62f8c527-1c01-0000-0080-ea04be658fb1).
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 BT.BK.CBS962T4 to 62f8c527-1c01-0000-0080-ea04be658fb1. 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. |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Wed Sep 03, 2008 3:58 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Hi,
As it says in error message:
1) check that you are using the right configmgr to manage broker(the first configmgr that broker was assigned)
2) if so your configmgr have messed the broker uuid and you have to correct it (use the Configuration Manager Proxy API BrokerProxy.setUUID() method to set the UUID)
Marko |
|
| Back to top |
|
|
| alagarsamy |
| Posted: Wed Sep 03, 2008 4:07 am Post subject: |
|
|
Newbie
Joined: 03 Sep 2008
Posts: 5
|
Hi
I have used the right configmanager name to connect via toolkit. It didn't displayed the Broker though I could see that through mqsilist command.
So I have craeted Broker with the same name using the toolkit and EG's as well.When I tried deploying flows,i got that erro as the Broker I have created has different UUID than what the old Broker has.
For some network reasons/I couldn't see run as option while starting the proxy exerciser,I cannot use that to connect to the server.
I think I need to use commands to delete and recreate as mentioned as the last option. Not sure why I couldn't see the Broker via toolkit though the mqsilist displayed it. |
|
| Back to top |
|
|
|
|
