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:
Oracle Coherence - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
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
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
Goal |
Solution |