WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Resolving problems when stopping resources

Use the advice given here to help you to resolve problems when you stop resources.

You cannot stop the broker

  • Scenario: You run the mqsistop command to stop the broker, but the system freezes, and does not stop any of the execution groups.
  • Explanation: One possible cause is that a message flow is being debugged and it is currently stopped at a breakpoint. WebSphere® Message Broker regards this as a message in flight situation, and refuses to stop the broker through the normal command.
  • Solution: Click Stop debugging in the Broker Application Development perspective of the WebSphere Message Broker Toolkit. After that operation has completed, the broker stops.

    If you cannot stop the debug session, end all execution group processes that are associated with that broker to allow the broker to stop. Your messages are backed out. Click Stop debugging after the broker restarts.

You cannot stop the broker queue manager

  • Scenario: You are trying to use the WebSphere MQ endmqm command to stop a broker queue manager on a distributed system, but it does not stop.
  • Explanation: In certain circumstances, attempting to stop a broker queue manager does not cause the queue manager to stop. This situation can occur if you have configured any message flows with multiple threads (you have set the message flow property Additional Instances to a number greater than zero).
  • Solution: If you want to stop the broker's queue manager, stop the broker by running the mqsistop command and specifying the -q parameter. (The -q parameter is not available on z/OS®.) This command runs the WebSphere MQ endmqm command on your behalf in a controlled fashion that shuts down the broker and the queue manager cleanly.

The execution group ends abnormally

  • Scenario: Your execution group processes end abnormally.
  • Explanation: When execution group processes end abnormally, they are restarted automatically by the bipbroker process. If an execution group process fails, it is restarted three times during each five-minute interval. The first five-minute interval begins when the execution group is first started. RetryInterval defaults to 5

    Remove the execution group from the broker configuration, deploy the broker configuration, then later add the execution group, and redeploy the broker configuration. The row is re-created and RetryInterval is set to its default value of 5.

  • Solution: To change the default value:
    1. Stop the broker.
    2. Change the value of the RetryInterval in the database table.
    3. Restart the broker.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:38


Task topicTask topic | Version 8.0.0.7 | au16580_