Cancel deployment

Canceling a deployment tells the Configuration Manager to assume that a broker will never respond to an outstanding deployment.

You might need to cancel a deployment because 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.

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 a deployment, you can manually remove outstanding deployment messages to ensure that they are not processed.

You can cancel a deployment in two ways:

Cancel deployment to a domain

Canceling a deployment to a domain has the following effects:
  • The Configuration Manager assumes that all brokers in the domain that have outstanding deployments will not respond.
  • The locks for all outstanding deployments in the domain are removed.
  • Deployment messages that have not yet been processed are not removed from any of the brokers in the domain by the Configuration Manager. For brokers that have successfully deployed a configuration, the deployed information remains on the broker.
When to use
Cancel a domain deployment only if both of these conditions are met:
  • You receive error message BIP1510 when you attempt a deployment.
  • None of the brokers that have outstanding deployments are responding.
When not to use
  • If a broker is merely taking a long time to respond to a deployment request. The broker might have been temporarily stopped, for example.
  • If other users might be deploying to the domain at the same time.
  • If only one broker is not responding, or a small number of brokers are not responding. In this case, cancel the deployment to individual brokers instead.

Cancel deployment to a broker

Canceling a deployment to an individual broker has the following effects:
  • The Configuration Manager assumes that the specific broker will not respond to outstanding deployments.
  • The locks for outstanding deployments to that broker only are removed.
  • The Configuration Manager attempts 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.
When to use
Cancel a domain deployment only if both of these conditions met:
  • You receive error message BIP1510 when you attempt a deployment.
  • The broker is not responding.
When not to use
  • If the broker is simply taking a long time to respond to a deployment request. The broker might have been temporarily stopped, for example.
  • The connected Configuration Manager is at Version 6.0 or later. If the version is earlier, canceling deployment to a specific broker has no effect; you must cancel the entire domain deployment instead.
Related concepts
Deployment overview
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009. All Rights Reserved.
Last updated : 2009-01-07 15:40:22

af02040_