The Configuration Manager allows only one deployment to be in progress to each broker at any one time. If for some reason a broker does not respond to a deployment request, subsequent requests cannot reach the broker, because, to the Configuration Manager, a deployment is still in progress.
Canceling deployment tells the Configuration Manager to assume that a broker will never respond to an outstanding deployment. In most cases, the action does not remove any deployment messages that have been sent to the broker, nor does it alter the running configuration of the broker. (Thus, for any brokers that have successfully deployed a configuration, the deployed information remains on the broker.)
If a broker subsequently does provide a response to an outstanding deployment that has been canceled, the response is ignored by the Configuration Manager, and an inconsistency subsequently exists between what is running on the broker and the information that is provided by the Configuration Manager.
Because of this risk of inconsistency, cancel a deployment only as a last resort, and only if you are sure that a broker will never be able to process a previous deployment request. However, before canceling deployment, you can manually remove any outstanding deployment messages to ensure that they are not processed.
When canceling deployment across the domain, the locks for all outstanding deployments in the domain are removed. When canceling deployment for a specific broker, the lock for that broker only is removed.
Canceling deployment is the equivalent of the 'force deploy' action in previous versions, except that cancel does not redeploy domain information.
Canceling the deployment to a domain tells the Configuration Manager to assume that all brokers in the domain that have outstanding deployments will not respond. If a broker later responds to an outstanding deploy that has been canceled, the response is ignored and there is an inconsistency between what is running on the broker and the information that is provided by the Configuration Manager.
When applied to a domain, canceling deployment does not remove deployment messages that have been sent to the brokers and does not change the brokers' running configuration.
Canceling the deployment to a single broker tells the Configuration Manager to assume that a specific broker in the domain that has an outstanding deployment will not respond. If a broker later responds to an outstanding deploy that has been canceled, the response is ignored and there is an inconsistency between between what is running on the broker and the information that is provided by the Configuration Manager.
When applied to an individual broker, canceling deployment causes the Configuration Manager to attempt to remove from the broker, deployment messages that have not yet been processed. This succeeds only if the broker and the Configuration Manager share the same queue manager, and if the message has not already been processed by the broker.