Hello,
All the components in the service (java, apache, & the Solid database engine) have to be running for the GUI to serve the web page & successfully login. So when the primary WCS was rebooted, the secondary wasn't able to reach the primary which triggered the fail-over event. On a reboot, the services on the primary came back & the secondary was able to fail-back. The Health Monitor(HM) component is responsible for making the call.
Heart Beat—Heart Beat submodule is responsible for maintaining communication between the primary and secondary HMs. Communication occurs over HTTPS (default port is 8082). The timeout value is 2 seconds. A retry mechanism has been implemented to retry establishing connectivity between the Primary-HM and Secondary-HM. If the HM does not receive a response after sending a heartbeat request within the timeout period, it retries establishing communication by sending another heartbeat request. The total number of retries is 3. After communication has not be established after 3 retries, the HMs take appropriate action.
Ram