ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MB V6 - Config Manager, Broker , Queue Manager and Database

Post new topic  Reply to topic
 MB V6 - Config Manager, Broker , Queue Manager and Database « View previous topic :: View next topic » 
Author Message
ivy112
PostPosted: Wed Aug 30, 2006 10:54 pm    Post subject: MB V6 - Config Manager, Broker , Queue Manager and Database Reply with quote

Newbie

Joined: 30 Aug 2006
Posts: 3

Hi,
My problem is solved but I would like to know the actual reason!! Here are the details:

On MB V6, we had some issues while deploying message flows(all MB related components are running on XP). Error message like "Config Manager is waiting for response for a previous deployement" was getting thrown each time.

[b]Step 1 :[/b] We created a new CM, Broker, QM(but used the old Broker database). Problem was still there.

[b]Step 2 : [/b]Created another set of all these components alongwith a new Broker Database and the Problem got resolved.

I read in the V6 manuals that the CM in V6 has nothing to do with the Broker database. So why did the deployment fail after step#1?

-Vijay
Back to top
View user's profile Send private message
MB12345
PostPosted: Thu Aug 31, 2006 6:32 am    Post subject: Reply with quote

Newbie

Joined: 28 Jul 2006
Posts: 6

Hi,


Solution1

->Open ConfigrationManagerProxyExcerciser and Connect to the ConfigManager (start -> programs -> IBM MB6.0 ->Java Api )
->Right Click on PubSubTopology and select 'Remove References to previously deleted Broker' .
->Specify the previously deleted broker name.


Thanks,
sss
Back to top
View user's profile Send private message
mqmatt
PostPosted: Fri Sep 01, 2006 4:53 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

Hmm.. perhaps the table definitions got corrupted or something?

The Config Manager doesn't have anything to do with the broker's database, but it's not the CM that's necessarily the problem here - the problem was that the broker didn't respond to the deployment request. The Config Manager prevents you from starting a second deployment to a broker if it hasn't heard back from the previous deployment - things would otherwise get messy.
-Matt
Back to top
View user's profile Send private message
ivy112
PostPosted: Mon Sep 04, 2006 1:21 am    Post subject: Reply with quote

Newbie

Joined: 30 Aug 2006
Posts: 3

Thanks for your replies! I will be careful next time not to play with CMs or Brokers
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MB V6 - Config Manager, Broker , Queue Manager and Database
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.