BIP1569
Severity
10 : WarningMessage
The Configuration Manager has removed any deployment lock associated with broker <insert_0>.Explanation
A request to cancel deployment was issued against broker <insert_0>. This was completed successfully, and consequently the Configuration Manager has discarded any outstanding deployment lock for that broker. It is now possible to send new deployment requests to that broker.
However, the Configuration Manager was unable to ensure that the original deployment message cannot be processed by the broker. If the broker has (or will) process this message and update its configuration as a result, the Configuration Manager will no longer be able to update its records to match and the broker will become out of sync with the Configuration Manager.Response
If the broker is permanently unavailable, no further action is required.
If the broker may be only temporarily unavailable, you must take steps to remove the deployment message from the broker's input queue. Ensure that the broker is stopped and on the broker machine issue (for example) 'amqsget SYSTEM.BROKER.ADMIN.QUEUE [qmgr]' where [qmgr] is the name of the queue manager on which the broker is running.
If you suspect that the broker has already processed the deployment message that has been cancelled, you must redeploy the affected resources in order to resynchronize the Configuration Manager's records with the broker.
In order to prevent the situation reoccurring, ONLY cancel deployment when there is no possibility that the broker can ever process the submitted deployment request.