How to Avoid Coherence Cluster Formation Delay Situation When a Virtual IP Address Is Involved (Doc ID 2941375.1)

Last updated on APRIL 15, 2024

Applies to:

Goal

Getting below mentioned error when starting ADMIN server with startWeblogic.sh script:

.
(thread=Cluster, member=n/a): Delaying formation of a new cluster; waiting for well-known nodes in cluster 'defaultCoherenceCluster' to respond>

[ACTIVE] ExecuteThread: 'x' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Error while starting cluster: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
  MemberSet=M<xxx>MemberSet(
    ThisMember=null
    OldestMember=null
    ActualMemberSet=MemberSet(Size=0
      )
    MemberId|ServiceJoined|MemberState|Version
    RecycleMillis=1200000
    RecycleSet=MemberSet(Size=0
      )
    )
)
        at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:3)
 




 

Solution

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