Default IpMonitor Timeout Configuration Can Lead To "Failure To Reach Address" Error Causing Nodes To Be Ejected From The Coherence Cluster
Last updated on SEPTEMBER 27, 2017
Applies to:Oracle Coherence - Version 3.7.1 and later
Information in this document applies to any platform.
The IpMonitor service in a node reports an error, "Failed to reach address xxxx within the IpMonitor timeout". There are log messages indicating that the IpMonitor could not reach a particular machine that list the Coherence nodes on that machine that are ejected from the cluster. For example, a member with Id=53, coincidentally in this case the senior member of the cluster, is acting as the IpMonitor on its server and reports the following:
These members have to be manually restarted.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms