| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Strange problem with UUID for Broker V5 |
« View previous topic :: View next topic » |
| Author |
Message
|
| whytec |
 Posted: Tue Apr 11, 2006 11:22 pm Post subject: Strange problem with UUID for Broker V5 |
 |
|
Apprentice
Joined: 28 Nov 2005
Posts: 26
Location: Brisbane Australia
|
Hi All,
I've seen many many posts about the UUID (BIP2045E) problem when trying to connect to the broker via the WBIMB5 toolkit, and have had the problem a few times myself and easily fixed it.
The problem I am facing now is quite extraordinary. I've just upgraded a server from V2.1 to V5. Took all the necessary precautions... deleted the broker and configmgr, dropped the database tables, deleted the queue managers and uninstalled V2.1 (and it worked cleanly for once  ).
I installed everything for V5 in the usual manner (done this quite a few times before), and then tried connecting the toolkit to the broker. Got the UUID mismatch problem so I thought "No sweat, I'll just delete the toolkit connection, delete the broker, and recreate them".
To my surprise, the same problem occurred. I noticed that the Broker kept the same UUID (I noticed that the broker identity UUID that the toolkit sent was different). So I thought that there must have been something hanging around that kept the broker UUID, and then it picked it up again after recreating it.
My next move was to delete the broker, drop the broker database, create the database and create the broker. Same problem, same UUID.
Then I tried deleting the broker and configmgr, dropping the databases, deleting the queue managers and uninstalling V5. I conducted an intensive search through the file system and registry for anything that contained this UUID that kept popping up. Nothing was found, so I thought I was safe.
I reinstalled and created everthing, but waited before I started the Broker and Configmgr services. I once again searched the file system, registry and Databases. Couldn't find the UUID anywhere. So I started the Broker and checked the registry for the UUID for the broker. It had EXACTLY the same UUID again!!!
I'm using Windows 2000 advanced server, WMB5 with CSD06, and MQSeries 5.3 with the latest patch.
I'm at a loss (and way beyond my deadline). Has anyone else heard of this happening before? |
|
| Back to top |
|
 |
| fazz |
| Posted: Tue Apr 11, 2006 11:37 pm Post subject: |
|
|
Centurion
Joined: 20 Feb 2004
Posts: 144
Location: England
|
What happens if you create a broker with a different name?
Or create the broker/configmgr databases with different names?
Just thinking the information must be being held some where..... |
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Apr 12, 2006 3:02 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Debris in the registry? Check HKLM\SOFTWARE\IBM\WebSphereMQIntegrator\2\<brokername>\CurrentVersion\BrokerUUID.
As fazz says, also try entering a different name for your broker. |
|
| Back to top |
|
|
| whytec |
| Posted: Wed Apr 12, 2006 3:48 pm Post subject: |
|
|
Apprentice
Joined: 28 Nov 2005
Posts: 26
Location: Brisbane Australia
|
| mqmatt wrote: |
Debris in the registry? Check HKLM\SOFTWARE\IBM\WebSphereMQIntegrator\2\<brokername>\CurrentVersion\BrokerUUID.
As fazz says, also try entering a different name for your broker. |
I searched the whole registry for the UUID and nothing was found. I'm going to do another file system search today to see if I can find the UUID now that the Broker is created again. |
|
| Back to top |
|
|
| whytec |
| Posted: Wed Apr 12, 2006 3:54 pm Post subject: |
|
|
Apprentice
Joined: 28 Nov 2005
Posts: 26
Location: Brisbane Australia
|
| fazz wrote: |
What happens if you create a broker with a different name?
Or create the broker/configmgr databases with different names?
Just thinking the information must be being held some where..... |
Tried this and it worked  I'm still going to try and get to the bottom of this though. I'll post here once I find out exactly where this information is being kept.
One thing I did notice was the difference in behaviour between the old broker and the new one. When I recreated the old broker, the registry entries were created and the UUID was added to the registry as soon as I started the broker. I started the new broker (different name, db and qmanager) and a UUID didn't appear in it's registry section until I connected the toolkit to the broker. Obviously there's some information hanging around somewhere in the system. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Thu Apr 13, 2006 12:41 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| Quote: |
| the UUID was added to the registry as soon as I started the broker |
As soon as you started the broker? Without deploying to it? Are you sure the queue manager and queues were deleted? The signs point to an old deploy message left over on the broker queue manager's SYSTEM.BROKER.ADMIN.QUEUE.
As soon as you started the new broker, it would have picked up the deploy message that was sent to the old broker, and as this was the first deploy to the new broker it would have picked up the same UUID as the broker before it.
-Matt |
|
| 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
|
|
|
|
