|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Problem creating a broker from toolkit |
« View previous topic :: View next topic » |
Author |
Message
|
mqsidude |
Posted: Wed Dec 29, 2004 6:25 am Post subject: Problem creating a broker from toolkit |
|
|
 Centurion
Joined: 22 Jan 2004 Posts: 148
|
Hi,
I have just installed WBI 5.0 on the following environment:
Windows 2000 SP4
MDAC 2.8
DB2 8.1.4
I have created the config manager and a broker. Both services are started succesfully but with following warning:
WBI.$SYS_mqsi ) An error occurred while opening LIL directory 'C:/Program Files/IBM/WebSphere MQ Integrator 2.1/jplugin'.
An error occurred while opening LIL directory 'C:/Program Files/IBM/WebSphere MQ Integrator 2.1/jplugin'. This directory may not exist, or may be unreadable by the broker.
Ensure that all directories contained in the LIL path are valid and readable by the broker.
Now i see that the specified folder is not existing under the install directory!
Now from the toolkit, i have created a domain connection and tried creating the broker under the boker topology. This action is failing with the an alert 'Execution Group is not running'. The event viewer shows the following error:
( ConfigMgr ) Broker WBI (UUID 6e141c1f-0101-0000-0080-9cdc341c18a6) running on WebSphere MQ queue manager WBI could not process an internal configuration message because the broker identity received in the message (UUID 8c67341f-0101-0000-0080-9cdc341c18a6) 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 (8c67341f-0101-0000-0080-9cdc341c18a6) that does not match the UUID of broker WBI running on WebSphere MQ queue manager WBI. There are two possible reasons for this. Either a user has accidentally specified queue manager WBI when defining another broker so that messages destined for the other broker have arrived at this broker, or the definition for broker WBI was deleted and recreated on the Message Brokers Toolkit which has the effect of giving broker WBI 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".
Any clues on the cause of the error is highly appreciated.
Thanks
-Crony |
|
Back to top |
|
 |
fschofer |
Posted: Wed Dec 29, 2004 6:34 am Post subject: |
|
|
 Knight
Joined: 02 Jul 2001 Posts: 524 Location: Mainz, Germany
|
|
Back to top |
|
 |
lillo |
Posted: Wed Dec 29, 2004 6:39 am Post subject: |
|
|
Master
Joined: 11 Sep 2001 Posts: 224
|
Are you migrating from v2.1 to v5.0? If so, there is a redbook covering the migration.
I found a similar problem when I tried to add a broker associated to a ConfigMgr to a new ConfigMgr. To solve this, just recreate the broker.
Other solutions, which I do not recommend, is modified the windows registry entry BrokerUUID.
Regards, _________________ Lillo
IBM Certified Specialist - WebSphere MQ |
|
Back to top |
|
 |
waugh |
Posted: Wed Dec 29, 2004 6:55 am Post subject: |
|
|
 Master
Joined: 19 Feb 2004 Posts: 225
|
|
Back to top |
|
 |
mqsidude |
Posted: Thu Dec 30, 2004 2:20 am Post subject: |
|
|
 Centurion
Joined: 22 Jan 2004 Posts: 148
|
Thank you all for your responses.
I have applied fix pack 4 and now am able to create the broker without any problems.
But the alerts view showed an alert 'Execution Group not running' for the 'default' execution group that got created along with the broker. I tried deploying it for a while but endedup with the same warning. I have created/deployed a new execution group and later deleted the 'default' execution group. As a guy who is trying to upgrade from WMQI 2.1, i did not understand why am not able to deploy the 'default' execution group. Any clues?
Thanks a lot,
Crony |
|
Back to top |
|
 |
fschofer |
Posted: Thu Dec 30, 2004 3:20 am Post subject: |
|
|
 Knight
Joined: 02 Jul 2001 Posts: 524 Location: Mainz, Germany
|
Hi,
add/deploy a message flow to the default EG and the message will disappear. (an empty bar file will also do it)
You will always get this message when you create a new EG.
Don't ask me why this is so.
Greetings
Frank |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|