My Oracle Support Banner

Changing Listen-Address from IP Address to Hostname or FQDN Results in Coherence Cluster Members Startup Failure. (Doc ID 2473070.1)

Last updated on JULY 28, 2020

Applies to:

Oracle Coherence - Version 3.7.1.1 to 12.2.1.3.0 [Release AS10g to 12c]
Oracle WebLogic Server - Version 10.3.6 to 12.2.1.3.0
Information in this document applies to any platform.

Symptoms

Customer has a cluster setup of two physical nodes hosting two OSB Managed Servers in the domain. The underlying WebLogic Server version is 12.2.1.3.0 and its bundled Coherence stack is 12.2.1.3.0 too. The customer configured listen addresses explicitly using IP Addresses. When they changed from IP Addresses to Hostname/FQDN as Listen Addresses, customer started seeing Coherence cluster (WKA) formation issue. When starting both the OSB servers on both the physical nodes, the first OSB Managed Server hosted on Node 1 comes to running mode. However the second OSB Managed Server hosted on the remote node, failed to join the Coherence Cluster. The corresponding logging indication of the second server is as follows...

Changes

Customer has replaced IP address with hostname or FQDN for the listen-address of the managed servers in the domain.

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!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.