WebSphere Message Brokers
File: an04402_
Writer: Bill Oppenheimer

Task topic

This build: July 31, 2007 21:33:19

Recovering after the Configuration Manager's queue manager fails on Windows, Linux, and UNIX systems

Use the procedure in this section only as a last resort.

If the failed queue manager was shared between a broker, User Name Server and Configuration Manager, re-create all three components, because each component creates different queues. For information on how to recover a shared queue manager, see Recovering after a shared queue manager fails.

If the Configuration Manager's queue manager fails and cannot be corrected using problem determination, or by the IBM Support Center, perform the following sequence of operations to re-create the queue manager:

  1. Ensure that no workbench users are deploying to brokers. You must wait until any such actions have completed.
  2. Stop all brokers that are using the Configuration Manager using the mqsistop command.
  3. Stop the Configuration Manager using the mqsistop command.
  4. Delete the Configuration Manager using the mqsideleteconfigmgr command, with the -q parameter to remove the queue manager.
  5. Re-create the Configuration Manager using the mqsicreateconfigmgr command. The mqsicreateconfigmgr command creates the queue manager and default queues automatically.
  6. Start the Configuration Manager using the mqsistart command.
  7. Start your brokers using the mqsistart command.
  8. Redeploy the domain configuration.

Related tasks
Recovering after the Configuration Manager's queue manager fails
Related reference
mqsicreateconfigmgr command
mqsideleteconfigmgr command
mqsistart command
mqsistop command
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:33:19

an04402_ This topic's URL is: