| Author |
Message
|
| my_mqseries |
 Posted: Sat Jul 15, 2006 10:10 am Post subject: Deployment Error |
 |
|
Apprentice
Joined: 03 May 2006
Posts: 31
|
Hi
In WBIMB 5.0 on Windows XP, when I am trying to deploy Bar file this is the error coming.
BIP2045E: Broker MBBRK (UUID eaa0db55-0c01-0000-0080-99c5942f0c26) running on WebSphere MQ queue manager MBBROKER.queue.manager could not process an internal configuration message because the broker identity received in the message (UUID affdec72-0c01-0000-0080-99c5942f0c26) did not match that of this broker.
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 (affdec72-0c01-0000-0080-99c5942f0c26) that does not match the UUID of broker MBBRK running on WebSphere MQ queue manager MBBROKER.queue.manager. There are two possible reasons for this. Either a user has accidentally specified queue manager MBBROKER.queue.manager when defining another broker so that messages destined for the other broker have arrived at this broker, or the definition for broker MBBRK was deleted and recreated on the Message Brokers Toolkit which has the effect of giving broker MBBRK a new, different UUID.
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 MQ Integrator online documentation section "Recovery and restart".
Can some one help me?
Cheers |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sat Jul 15, 2006 11:07 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I thought the directions given in the message are pretty clear. What is it that you do not understand?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| my_mqseries |
| Posted: Sat Jul 15, 2006 11:18 am Post subject: |
|
|
Apprentice
Joined: 03 May 2006
Posts: 31
|
Thanks for your reply.
I think the problem is
the definition for broker MBBRK was deleted and recreated on the Message Brokers Toolkit which has the effect of giving broker MBBRK a new, different UUID.
How can I fix this please? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jul 15, 2006 3:32 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| my_mqseries wrote: |
Thanks for your reply.
I think the problem is
the definition for broker MBBRK was deleted and recreated on the Message Brokers Toolkit which has the effect of giving broker MBBRK a new, different UUID.
How can I fix this please? |
As it says in your first post:
- remove broker from toolkit
- use mqsideletebroker to delete the broker
- use mqsicreatebroker to recreate the broker
- add back to toolkit
- do a full deploy
And remember that in V5 you do not have the possibility to use the java configmgr proxy to remove references to a previously deleted broker.
So make sure you follow the manuals to the letter.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| my_mqseries |
| Posted: Sat Jul 15, 2006 7:15 pm Post subject: |
|
|
Apprentice
Joined: 03 May 2006
Posts: 31
|
Hi
I did follow what you have given. However I get the same error again.
BIP2045E: Broker MBBRK (UUID eaa0db55-0c01-0000-0080-99c5942f0c26) running on WebSphere MQ queue manager MBBROKER.queue.manager could not process an internal configuration message because the broker identity received in the message (UUID affdec72-0c01-0000-0080-99c5942f0c26) did not match that of this broker.
I think I am missing something very seriously. A question. After creating Broker from the command line, I am creating MBBRK directly in Domains.
Am I right. Sorry I am very new to WBIMB.
Thank You |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Jul 16, 2006 2:45 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
In V5 you may have to delete any reference to that broker (after having used mqsideletebroker) from the config manager's DB. As I said there is no configmgr proxy in V5 to automate that task for you.
Get in touch with your IBM representative and seek some help in eliminating that problem...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| my_mqseries |
| Posted: Sun Jul 16, 2006 7:07 am Post subject: |
|
|
Apprentice
Joined: 03 May 2006
Posts: 31
|
Hi
I did remove the references in Config Mgr and done everything afresh. Now I am getting this error.
( MBBRK ) Broker MBBRK (UUID 78377777-0c01-0000-0080-99c5942f0c26) was unable to retrieve an internal configuration response message for execution group '$SYS_mqsi' within the 360 second Configuration Timeout.
The execution group did not respond within the Configuration Timeout period. A negative response is returned to the Configuration Manager for this execution group. The Configuration Timeout is the maximum length of time that an execution group is allowed to apply a deployed configuration change. By default the Configuration Timeout period is 300 seconds. You can increase (or decrease) the timeout by using the mqsichangebroker option, ConfigurationTimeout. This will not resolve any underlying problem with the deployed message, but can be used to reduce the response turnaround time or increase it to allow for large and complex deployments.
Investigate why the execution group was unable to respond before being timed out. Use the system log messages to determine if there is a problem with the execution group. You should check that your system is not running short of resources, for example, you may need to increase the WebSphere Business Integration log size. Reducing the complexity of the deploy by reducing the number of execution groups may also help to alleviate this problem. Correct the problem and redeploy the broker's configuration from the Message Brokers Toolkit. If there are no other failure diagnostics then you should consider increasing the Configuration Timeout, increase this value in units of 300 until this message no longer occurs. Contact your IBM support center if
I am trying this on my laptop. I have only one bar file to delpoy and see how is it going. I did check the Processes running under Task Manager. I can see bipborker, bipcofigmgr, biphttplistener, bipservice - 2, DataFlowengine.
Do you know why is this error coming?
Thank You |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Jul 16, 2006 9:23 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You might need to recycle all the elements: config manager, broker.
Once you did that (make sure all DataflowEngine processes are gone when the broker is shutdown) try again.
And make sure the flow you are trying to deploy is not in debug at the time of deployment!
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
