How To Verify That the IPMonitor Feature Works Correctly Between the Machines Coherence Cluster Members Are Running On
(Doc ID 1936105.1)
Last updated on AUGUST 11, 2021
Applies to:Oracle Coherence - Version 3.6.0 and later
Oracle Access Manager - Version 18.104.22.168.0 and later
Oracle SOA Suite - Version 22.214.171.124.0 and later
Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.
Coherence 3.6 introduced a new feature implementing death detection on machine level called "IP Monitor". For a description of this feature please refer to <Note:1526745.1>, What Is The Purpose Of IpMonitor In A Coherence Cluster?
Coherence ships with a simple test utility class:
which allows to test if the target machines had been setup correctly, so Coherence can use the IP Monitor feature.
This document explains how to use com.tangosol.net.Ping to verify that the target machines have been setup correctly and uses an example of an environment with a problem to demonstrate the type of troubleshooting steps that should be taken.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|1. Description Of The Example Network Topology|
|2. Verify That The NICs Are Bound To The Expected IP Addresses Of The Subnet xx.xx.yy.yy/24 On Each Compute Node|
|3. On "oel651" Test The "Reachability" Of The Other Compute Nodes|
|4. Repeat the Above Test From Each Remaining Compute Node To All of The Other Compute Nodes|
|5. Check Whether xx.xx.10.11 Can Be Reached with the Operating System's Ping Utility|
|6. Check If There Is a Firewall Which Is Blocking the Pings Sent By com.tangosol.net.Ping Which Uses java.net.InetAddress.isReachable|
|7. Shutdown The Firewall On oel651 Which Is Blocking Ping Messages Sent By com.tangosol.net.Ping using java.net.InetAddress.isReachable|