BIP1570
Severity
10 : WarningMessage
The Configuration Manager has removed all deployment locks.Explanation
A request to cancel deployment was issued against all brokers in the domain. This was completed successfully, and consequently the Configuration Manager has discarded all outstanding deployment locks that currently exist. It is now possible to send new deployment requests to all brokers in the domain.
However, the Configuration Manager was unable to ensure that any outstanding deployment messages cannot be processed by the affected brokers. If these brokers have (or will) process these messages and update their configurations as a result, the Configuration Manager will not be able to update its records to match and the brokers will become out of sync with the Configuration Manager.Response
If the brokers that had outstanding deploys are permanently unavailable, no further action is required.
If the brokers that had outstanding deploys may be only temporarily unavailable, you must take steps to remove the deployment messages from the brokers' input queues. Ensure that the brokers are stopped and on the broker machines issue (for example) 'amqsget SYSTEM.BROKER.ADMIN.QUEUE [qmgr]' where [qmgr] is the name of the queue manager on which each broker is running.
If you suspect that one or more brokers have already processed a deployment message that has been cancelled, you should redeploy the affected resources in order to resynchronize the Configuration Manager's records with the broker(s).
In order to prevent the situation reoccurring, ONLY cancel deployment when there is no possibility that a broker can ever process the submitted deployment request.