OAM Server Throws CoherenceTtimeout Errors at Startup When Configured on the Same Machine as AdminServer Using Multiple IPs per NIC
Last updated on DECEMBER 18, 2017
Applies to:Oracle Access Manager - Version 220.127.116.11.5 and later
Information in this document applies to any platform.
One of the OAM managed servers and AdminServer are sharing the same machine configured with multiple IP addresses on a single NIC. AdminServer is using a VIP address which is mapped to one of the 2 IP addresses, OAM server is mapped to the second IP address.
In this configuration, all the other OAM server nodes which are located on separate physical machines are able to join the coherence cluster and start successfully, however, the one located on the same machine as AdminServer server fails to start throwing Coherence errors like below:
From what was noticed this happens whenever AdminServer is started first and is seen as the senior member in the Coherence cluster, followed by oam server startup.
If the OAM server in cause was moved to on different physical host there were no coherence errors at startup. Similarly, if all the OAM managed servers were started while keeping AdminServer down all of them started successfully.
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