oam_server Fails When Starting In A Cluster Environment

(Doc ID 2174707.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Access Manager - Version and later
Information in this document applies to any platform.


oam_server2 in cluster fails during starting

OAM Deployed with two nodes in a cluster. When oam_server2 servers oam_server deployment fails to start.
Followed the document OAM Deployments Failing In New OAM Domain Caused By: java.net.UnknownHostException: AdminServerHostname is not a local address (Doc ID 2114147.1)
in oam_server1
-Dtangosol.coherence.wka1=SVIAM0000101NP.nbndc.local -Dtangosol.coherence.wka2=SVIAM0000138NP.nbndc.local -Dtangosol.coherence.localhost=SVIAM0000101NP.nbndc.local -Djava.security.egd=file:/dev/./urandom

in oam_server2
-Dtangosol.coherence.wka1=SVIAM0000101NP.nbndc.local -Dtangosol.coherence.wka2=SVIAM0000138NP.nbndc.local -Dtangosol.coherence.localhost=SVIAM0000138NP.nbndc.local -Djava.security.egd=file:/dev/./urandom

After implementing the change oam_server2 starts successfully. However if starting the servers parallely still getting the same error message. If starting the servers one after the other all works fine.

#### <oam_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <0000LMoe^vcFc5YzLoZR8A1NUWQU000004> weblogic.application.ModuleException:
  at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1529)
  at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
  at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)


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