OAM Application Is Failing To Start with ClassCastException After Coherence Stopping Cluster Service And Restarted Due To Communication Delays.
Last updated on JUNE 03, 2017
Applies to:Oracle Coherence - Version 18.104.22.168 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms