Probing Algorithm and Functionality

• WebSphere MQ Manager

  • Sleeps for Thorough_probe_interval.

  • Connects to the Queue Manager, creates a temporary dynamic queue, puts a message to the queue, and then disconnects from the Queue Manager. If this fails, then the probe will restart the Queue Manager.

  • If all Queue Manager processes have died, pmf will interrupt the probe to immediately restart the Queue Manager.

  • If the Queue Manager is repeatedly restarted and subsequently exhausts the Retry_count within the Retry_interval, then a failover is initiated for the Resource Group onto another node.

• Other WebSphere MQ components (chi, csv & trm)

  ---

  Note –

  The probing algorithm and functionality for the Channel Initiator, Command Server and Trigger Monitor all behave the same. Therefore the following text simply refers to these components as resource.

  ---

  • Sleeps for Thorough_probe_interval.

  • Dependent on the Queue Manager, if the Queue Manager fails the resource will fail and get restarted after the Queue Manager is available again.

  • If the resource has died, pmf will interrupt the probe to immediately restart the process.

  • If the resource is repeatedly restarted and subsequently exhausts the Retry_count within the Retry_interval then a failover is not initiated onto another node because Failover_enabled=FALSE has been set. The resource will be restarted.

• WebSphere MQ Listener

  • Sleeps for Thorough_probe_interval

  • Check whether the runmqlsr process associated with the Queue Manager and Port is running.

  • The listener can accommodate several port numbers under the same pmftag. If a listener for a particular port is found to be missing, the probe will initiate a restart of that listener without affecting the other listeners.

    Although the resource can accommodate several listeners, all listeners would need to fail before the resource is restarted. This provides a granular restart mechanism for a resource that has several listeners running.

  • If the resource is repeatedly restarted and subsequently exhausts the Retry_count within the Retry_interval, then a failover is not initiated onto another node because Failover_enabled=FALSE has been set. The resource will be restarted.