| Author |
Message
|
| harish6185 |
 Posted: Tue Apr 08, 2008 12:06 am Post subject: configuration manager inconsistane |
 |
|
Novice
Joined: 05 Mar 2008
Posts: 16
|
hi,
i think our configuration manager has become inconsistant. changes are not getting reflected even after deploying the changed sources.
getting an alert that " waiting for a response from the configuration manager"
would restarting the configuration manager resolves this problem, if so could you please tell me how to restart the configuration manager?
would restarting the configuration manager effect the brokers under it?
please clarify all my doubts.
thank you |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Tue Apr 08, 2008 12:38 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
its time up, better go through the documents throughly....
would restarting the configuration manager effect the brokers under it?
No it wont
you can restart using mqsi commands
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 08, 2008 1:01 am Post subject: Re: configuration manager inconsistane |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| harish6185 wrote: |
getting an alert that " waiting for a response from the configuration manager"
would restarting the configuration manager resolves this problem |
A relevant question is "why is the configuration manager not responding"?
 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| harish6185 |
| Posted: Tue Apr 08, 2008 1:14 am Post subject: Re: configuration manager inconsistane |
|
|
Novice
Joined: 05 Mar 2008
Posts: 16
|
this problem has aroused after cancelling the outstanding deployments.
we were made to cancel the outstanding deploymanets, because we were not able to redeploy the sources due to the following error
BIP1510E: Deployment failed; a deployment is already in progress to broker
plz help me in this regard |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 08, 2008 1:29 am Post subject: Re: configuration manager inconsistane |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| harish6185 wrote: |
we were made to cancel the outstanding deploymanets, because we were not able to redeploy the sources due to the following error
BIP1510E: Deployment failed; a deployment is already in progress to broker
|
Ok, so the question is in fact why was the broker not responding.... 
(I'm guessing you waited a little while for the in-progress deploy to finish with no sucess? If not, I think I've found your problem)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| harish6185 |
| Posted: Tue Apr 08, 2008 1:56 am Post subject: Re: configuration manager inconsistane |
|
|
Novice
Joined: 05 Mar 2008
Posts: 16
|
No i have waited for about 2 hours before cancelling the outstanding deployment.
Actual error description is as follows:
BIP1510E: Deployment failed; a deployment is already in progress to broker DHUB01BR
The Configuration Manager was asked to deploy to broker DHUB01BR, but this could not be attempted because it has not yet received a response to a previous deployment request submitted to that broker. To ensure that the deployed configuration is consistent with the reported configuration, the more recent deployment request has been discarded.
Note that if you are attempting to deploy the publish/subscribe topology or topic hierarchy, no brokers in the domain will have received the new deployment message. There can be no outstanding deploys in the domain before deployment of such a configuration can occur.
Wait for the outstanding deploy to complete before retrying the operation. The Event Log Editor or Configuration Manager Proxy may be used to check that all responses to the outstanding deploy have been received and processed. If the outstanding deploy does not fully complete in a suitable period of time, check that all brokers exist and are running, all WebSphere MQ queue managers are running, and that all channels between queue managers are started. Also check that deploy messages have been correctly delivered to the target brokers, and have not been put to the dead letter queue. Correct any problems you find. If it still does not complete, then cancel the deploy operation; either (a) right-click the broker in the Message Brokers Toolkit and select the 'Cancel Deployment' option, or (b) use mqsideploy with the -c option, or (c) use the BrokerProxy.cancelDeployment() method in a Configuration Manager Proxy application. Note that cancelling the deployment operation does not stop the deployment message from being processed by the broker; it simply forces the Configuration Manager to remove any outstanding deployment locks that may be associated with the broker. If a broker subsequently processes a deployment message that has been cancelled using this technique, the deployed configuration may become inconsistent with the reported configuration.
i have checked all the things which were mentioned in the error description.
everything is fine, up and running.
(I'm guessing you waited a little while for the in-progress deploy to finish with no sucess? If not, I think I've found your problem)
could you please tell me what have you found about the current problem?
thankyou very much |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Tue Apr 08, 2008 2:19 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
please check if the broker is getting abended. and check the system logs too 
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| MrSmith |
| Posted: Tue Apr 08, 2008 6:43 am Post subject: |
|
|
Master
Joined: 20 Mar 2008
Posts: 215
|
| Quote: |
| and check the system logs too |
Would agree here, it could be something to do with the Queuemanagers that your broker or config manager are on (depending on what version you are running v5 and V6 have different config possibilites). It could be that your DB is not accessible for some reason hence the broker / config mgr componnets could be in limbo. Event logs / System logs would be first place I'd look then the abend logs and slowly slowly catchee monkey. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Apr 08, 2008 1:21 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And make sure the broker qmgrs have a default path back to the config qmgr. Make sure that channel back to the config mgr has no problems and is running...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Apr 08, 2008 7:28 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
and don't use the cancel option on deploys unless you are 1000% certain the broker has not yet grabbed the deploy request message from the config manager. At IMPACT the Hursley folks said its real dangerous in WMB versions prior to 6.1.
Moved to the correct forum.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Apr 09, 2008 12:14 pm Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| PeterPotkay wrote: |
| At IMPACT the Hursley folks said its real dangerous in WMB versions prior to 6.1. |
Yeah, I know 
The reason is that "cancel deploy" simply tells the CM to ignore the outstanding deployment message. So if the broker subsequently picks up that cancelled deployment message, the two components can become out of sync.
In v6.0 the problem was alleviated somewhat by having the CM attempt to pull back (MQGET) the deployment message from the broker, but this only works if the CM and broker are sharing the same queue manager.
In v6.1, the broker and CM will periodically synchronize themselves so it's not really a problem. |
|
| Back to top |
|
|
| broker_new |
| Posted: Thu Apr 10, 2008 4:42 am Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
I got this problem before .
May be this will be useful for you.
My Broker and Configuration manager exists on different queue managers and the sender recevier channels between them are inactive.
So wheni started the channels are started the problem is solved.
_________________
IBM ->Let's build a smarter planet |
|
| Back to top |
|
|
| vkpham |
| Posted: Tue Apr 15, 2008 10:23 am Post subject: This will resolve the Config manager inconsistency |
|
|
Newbie
Joined: 15 Apr 2008
Posts: 1
|
I hope this will help you
I encounter this exact problem before on Windows 2000 Adv Servers. I had 2 Message Brokers (one for each box for load balance) and cannot deploy a BAR to any of the brokers. I encounter the same error message as “harish6185” had mentioned. And yes, my sender/receiver channel between the Configuration Manager and the Brokers are active. I was able to resolve this issue by restarting both of the Windows servers. |
|
| Back to top |
|
|
|
|
