My Oracle Support Banner

Oracle Access Manager 11g R2PS3 (OAM oam_server Fails When Starting In A Cluster Environment (Doc ID 2174707.1)

Last updated on OCTOBER 17, 2019

Applies to:

Oracle Access Manager - Version and later
Information in this document applies to any platform.
Oracle is not responsible for instructions/information from 3rd party sites that may be contained in this KM note.


oam_server2 in cluster fails during starting

Oracle Access Manager 11g R2PS3 (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 in oam_server1
-Dtangosol.coherence.wka1=<CLUSTER_NAME> -Dtangosol.coherence.wka2=<CLUSTER_NAME> -Dtangosol.coherence.localhost=<CLUSTER_NAME>

in oam_server2
-Dtangosol.coherence.wka1=<CLUSTER_NAME> -Dtangosol.coherence.wka2=<CLUSTER_NAME> -Dtangosol.coherence.localhost=<CLUSTER_NAME>

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)'> <> <> <VALUE> 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.