My Oracle Support Banner

oam_server Fails When Starting In A Cluster Environment (Doc ID 2174707.1)

Last updated on SEPTEMBER 02, 2018

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: AdminServerHostname is not a local address (Doc ID 2114147.1)
in oam_server1
-Dtangosol.coherence.wka1=cluster-abc.efg.local -Dtangosol.coherence.wka2=cluster-abc.efg.local -Dtangosol.coherence.localhost=cluster-abc.efg.local

in oam_server2
-Dtangosol.coherence.wka1=cluster-abc.efg-1.local -Dtangosol.coherence.wka2=cluster-abc.efg-1.local -Dtangosol.coherence.localhost=cluster-abc.efg-1.local

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(
  at weblogic.servlet.internal.WebAppModule.start(
  at weblogic.application.internal.flow.ModuleStateDriver$


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.