Federated Caches Failed To Connect To Remote Peer: java.lang.IllegalStateException: Participant configured with name 'PRIMARY' responded with Cluster name of 'SECONDARY'
(Doc ID 3072188.1)
Last updated on FEBRUARY 20, 2025
Applies to:
Oracle Coherence - Version 12.2.1.4.0 and later Information in this document applies to any platform.
Symptoms
Newly started federated caches are unable to establish connections with remote peers.
The issue is intermittent but occurs regularly in the automated test environment.
The cluster "PRIMARY" is hosted on HOST-A, while the cluster "SECONDARY" is hosted on HOST-B.
Log entries indicate that the FederatedxxCache on PRIMARY attempts to connect before its peer, resulting in "connection refused" errors.
The NameService on SECONDARY for services begins listening for connections.
The FederatedxxCache on PRIMARY experiences a change in failure messages, indicating that the "Service FederatedxxService could not be located via NameService lookup."
The FederatedxxCache on SECONDARY successfully registers with the NameService and joins the cluster, but the connection to PRIMARY is not established within the expected timeframe.
The FederatedxxCache on PRIMARY reaches the 20-minute timeout and terminates the connection attempt.
Changes
Cause
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
