Posted: Fri Feb 17, 2006 11:51 pm Post subject: broker instance shown as not started in toolkit.......
Novice
Joined: 29 Jan 2006 Posts: 15
I have 3 broker instances created in the same domain in the WBIMB5 toolkit. I have the physical brokers created, queue managers/connectivity taken care of. I can see 2 brokers as started and the third one as not started in the toolkit. The reality is that all the three brokers are running when verified from the command line.
Is there any limitation on the no. of brokers that can be created. I'm running on Windows XP Pro SP2.
Looks like the configmgr is not deploying the msgflow to the third broker. The event log tells me that the configmgr is trying to deploy a config to a broker that no longer exist.
I deleted the DB tables by mistake for one of the brokers. Hence that broker STOCK_BRK was left in a quasi state w.r.t configmgr. I couldn't do any successful deploys for the broker that are subsequently created.
My question boils down to this -
How to cleanup the configmgr of any broker related data(QM names, DB info) that no longer exist?
Joined: 04 Aug 2004 Posts: 1213 Location: Hursley, UK
Glad you solved the problem. For future reference, the following two topics might come in useful for tips on removing deleted brokers from the Config Manager:
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