MQSeries.net :: View topic

anantha sreenivasan · Posted: Sun Sep 30, 2007 9:34 pm Post subject:

I have a broker named Broker1 with Execution Group BROK_EG1. I depolyed two message flows to it. Now when try to deploy a message flow to another broker say Broker2 in the same broker domain as Broker1, I get the following warning

BIP1510E: Deployment failed; a deployment is already in progress to broker BROKER2

The Configuration Manager was asked to deploy to broker BROKER2, 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.

I cancelled all outstanding deployment against this broker and started afresh. Even after that I get the same problem. Can somebody please advise?