Probing Algorithm and Functionality

Sun Cluster Broker

Sleeps for Thorough_probe_interval.

Test the RDBMS or Queue Manager has been restarted. If the RDBMS has
been restarted, then the whole Resource Group will be restarted. If the Queue Manager
has been restarted, then the Broker is stopped and waits until the Queue Manager is
restarted, after which the Broker is restarted.

If the RDBMS and Queue Manager have not been restarted, then a check
against bipservice is made. If bipservice is
lost, then the probe will restart the Broker.

If bipservice is available, then the probe checks
that the queue names for SC3_IN and SC3_OUT are
valid and empty, puts a test message to SC3_IN, and checks that
the message flows to SC3_OUT by checking that the CURDEPTH for SC3_OUT is equal to 1. If this test fails, then
the probe will restart the Broker.

If the Broker 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.

Sun Cluster UserNameServer

Sleeps for Thorough_probe_interval

If bipservice for the UserNameServer is lost, then
the probe will restart the UserNameServer.

If the UserNameServer 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.