OAM 126.96.36.199 OAM Managed server fails to restart with com.tangosol.net.RequestTimeoutException
Last updated on OCTOBER 18, 2017
Applies to:Oracle Access Manager - Version 188.8.131.52.5 and later
Information in this document applies to any platform.
On : 184.108.40.206.5 version, Configuration Service
In 2 node OAM cluster (on Solaris SPARC platform), OAM managed server fails to join the cluster on restart and deployment of oam-server.ear deployments goes to failed status.
The oam managed serve logs will contain error as noted below -
Admin + Manged server (oam_server1)
Both nodes come up ok when started in this order for the first time: Adminserver --> oam_server1 -> oam_server2
OAM application deployments start to fail when one of the nodes in the OAM cluster is restarted.
The OAM nodes fail to join the cluster randomly on restart.
For example, the sequence is -
oam_server1 (RUNNING) and oam_server2 (RUNNING)
oam_server1 (SHUTDOWN) and oam_server2 (RUNNNING)
oam_server1 (RESTART) and oam_server2 (RUNNING).
oam_server1 coherence communication issues and oam apps don't initialize.
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