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

Recovering after the broker fails

Check what recovery procedures are available, according to what has failed.

Try to get to the root of the problem first, using the diagnosis techniques described throughout the Troubleshooting and support section of the information center. If your problem cannot be resolved using these techniques, contact your IBM® Support Center. Use the procedure in this section only as a last resort.

If you are able to recover, and can start the broker again, the broker attempts to recover and re-establish all sessions with CMP applications that were active at the time of failure. CMP applications include the WebSphere® Message Broker Explorer, the WebSphere Message Broker Toolkit, and applications that you have written to this API.

If you cannot correct the current problem by using problem determination, complete the following sequence of operations to re-create the broker:

  1. Stop the broker by using the mqsistop command.
  2. Stop the broker queue manager by using the endmqm command.
  3. Delete the broker by using the mqsideletebroker command.
  4. Re-create the broker by using the mqsicreatebroker command.
  5. Start the broker by using the mqsistart command.
  6. Redeploy all resources to 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:16


Task topicTask topic | Version 8.0.0.7 | an04380_