OAM Application Is Failing To Start with ClassCastException After Coherence Stopping Cluster Service And Restarted Due To Communication Delays.
(Doc ID 2196227.1)
Last updated on FEBRUARY 28, 2019
Applies to:Oracle Coherence - Version 220.127.116.11 and later
Information in this document applies to any platform.
OAM servers are not getting policy store initialized and failed to create sessions. This is happening intermittently and servers are not joining to the OAM services cluster even after restarting. In the first place servers are crashing or evicted from the cluster when the OAM applications class loader errors with NCDFE and due to high communication delays (latency problems) in the network between the VM hosted servers.
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