Resolving problems that occur after deployment of message flows
Advice for dealing with some common problems that can arise after deploying message flows or message sets.
You are not notified of the result of a deploy
- Scenario: After you have closed the Broker Topology editor, saved your changes, and requested a deploy, you are not notified of the result of a configuration deploy.
- Explanation: When you close the editor, the notification link with the Configuration
Manager is broken, so that the workbench is not notified of the deploy result. This is the same for any eventual failure notifications.
- Solution: To ensure that you receive any notification, save the editor without closing it and wait for the alert Waiting for answer from Configuration Manager to disappear. This alert is removed automatically when the editor receives all expected responses from the Configuration
Manager.
You do not receive confirmation that the deployment was successful
- Scenario: You have initiated deployment but have not received confirmation that the deployment was successful.
- Solution: Assume that communications from the workbench to the Configuration
Manager are working, because the workbench gives an error immediately if this link fails. Follow these steps to find out if there is a communication problem that stops the receipt of deployment confirmation:
- Stop the broker using the mqsistop command.
- On the broker queue manager, check the SYSTEM.BROKER.ADMIN.QUEUE queue. If there are messages on this queue, there might be a broker error; look in the local error log on the broker's system. If the queue is empty, continue with the next step.
- Redeploy your message flow.
- Recheck the SYSTEM.BROKER.ADMIN.QUEUE queue on the broker queue manager. If the queue depth has not increased, there is a problem with the channel between the Configuration
Manager and the broker; check the WebSphere® MQ logs. If the queue depth has increased to one, continue with the next step.
- Stop the Configuration
Manager, then start the broker.
This allows the broker to process the configuration change and send a response. Wait for the broker to process the message; this might take some time. (If the message takes more than five minutes to process, there is a problem with the deployed message and failure messages are displayed in the local error log on the broker's system indicating the reason for the failure.)
- Check the SYSTEM.BROKER.ADMIN.REPLY queue on the Configuration
Manager's queue manager. This queue should contain a response. If it does not, check that the channel from the broker to the Configuration
Manager is running.
- Restart the Configuration
Manager.
- Check that the messages are read from the SYSTEM.BROKER.ADMIN.REPLY queue on the Configuration
Manager's queue manager. If they are not, check the local error log on the Configuration
Manager's system for errors.
- Refresh the Event Log editor in the workbench. You should now get a reply.
You cannot see any deployed message flows
- Scenario: After you deploy a broker archive (BAR) file, you cannot see any deployed message flows under the execution group.
- Explanation: After deployment, an information window should tell you whether deployment has been started successfully on the Configuration
Manager. When the deploy has started, the time it takes to complete depends on your configuration size and the workload on your computers. However, if, after a while, no deployment-related messages are displayed in the Event Log editor, it means that the broker has not responded to the deployment request.
- Solution: Check that the broker is running and that all WebSphere MQ queue managers and channels between the Configuration
Manager and the broker are running. If the messages are present in the Event Log editor, see if any errors have occurred that mean that your changes were not activated.
A deleted broker remains in the domains navigator
- Scenario: After you have deleted a broker and deployed changes, the broker remains in the domains navigator.
- Explanation: If you did not receive any failure response indicating that the deletion failed, and the Event Log editor has been automatically refreshed with a set of messages about the deployment result, the deletion succeeded but the workbench has not been notified of this deletion.
- Solution: For the broker topology to reflect the actual Configuration
Manager content, refresh the broker topology. If the broker topology is open, click Revert.