title: Websphere MQ clustering
body: <p>I'm pretty new to websphere MQ, so please pardon me if I am not using the right terms. We are doing a project in which we need to setup a MQ cluster for high availability.</p>
  
  <p>The client application maintains a pool of connection with the Queue Manager for subscribers and publishers. Suppose we have two Queue Managers in a cluster hosting the queues with the same names.  Each of the queue has its own set of subscribers and publishers which are cached by the client application. Suppose one of the queue manager goes down, the subscribers and publishers of the queues on that queue manager will die making the objects on client application defunct. </p>
  
  <p>In this case can the following scenarios taken care of?</p>
  
  <p>1] When first QueueManager crashes, the messages on its queues are transferred to other queuemanager in the cluster</p>
  
  <p>2] When QueueManager comes up again, is there any mechanism to restore the publishers and subscribers. Currently we have written an automated recovery thread in the client application which tries to reconnect the failed publishers and subscriber. But in case of cluster setup, we fear that the publishers and subscribers will reconnect to the other running qmanager. And when the crashed queuemanager is restored, there will be no publishers and subscribers to it.</p>
  
  <p>Can anybody please explain how to take care of above two scenarios? </p>