|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Unable to Deploy the message flow |
« View previous topic :: View next topic » |
Author |
Message
|
redredred |
Posted: Mon May 07, 2007 10:31 am Post subject: Unable to Deploy the message flow |
|
|
Novice
Joined: 27 Feb 2007 Posts: 21
|
Hello guys, I am unable to deploy a message flow, I have pasted what the error says, can you please guys help me out
"BIP1510E: Deployment failed; a deployment is already in progress to broker SABKR
The Configuration Manager was asked to deploy to broker SABKR, 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, (b) use mqsideploy with the -c option, or (c) or 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."
cheers
preetham |
|
Back to top |
|
 |
jbanoop |
Posted: Mon May 07, 2007 12:38 pm Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005 Posts: 401 Location: SC
|
try cancelling the outstanding deployment and try again. this is because the broker has not replied back to the config mgr regarding the previous deployment.
it would also be advisable to check the communication b/w the config mgr machine and the broker machine are up and both components are running. |
|
Back to top |
|
 |
Mensch |
Posted: Mon May 07, 2007 5:42 pm Post subject: |
|
|
Disciple
Joined: 17 Jul 2005 Posts: 166
|
Hi Preetham,
Restart Broker and Config Manager services and try deploying your flow.
If the same problem persists then there is problem with the communication between Config Mgr Queue manager and Broker Queue manager.
Check the transmission queue name at both queue manager.
It should be same as remote(Broker or ConfigManager) Queue manager. _________________ Thanks and Regards ,
Mensch |
|
Back to top |
|
 |
mqmatt |
Posted: Tue May 08, 2007 3:18 am Post subject: |
|
|
 Grand Master
Joined: 04 Aug 2004 Posts: 1213 Location: Hursley, UK
|
Mensch is correct. But do what the error message says; that's why it was written
Pay particular attention to the last couple of sentences. Ensure that the SYSTEM.BROKER.ADMIN.QUEUE is empty after cancelling deployment.
-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
|
|
|
|