When Coherence Cluster is Restarted, Coherence*Web cache service oracle.coherence.web:DistributedSessions may not be restarted on the storage node.
(Doc ID 2671754.1)
Last updated on MAY 11, 2022
Applies to:Oracle Coherence - Version 3.7.1 to 220.127.116.11.0 [Release AS10g to 12c]
Oracle WebLogic Server - Version 10.3.6 to 18.104.22.168.0
Information in this document applies to any platform.
Customer was noticing that after a network outage, the Coherence*web distributed session service was not joining back the cluster. But all the other services are joining back to the cluster. The problem is that when the communication downtime was solved and all Coherence instances join the cluster again, the user still sees "No storage-enabled" errors at WebLogic instances, application nodes. The logs shown left the cluster messages, but not seen the Member Joined the designated cache service.
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