OAM 11g: New OAM Managed Server Did Not Start As Expected - ERROR - Get security module failed

(Doc ID 1515177.1)

Last updated on MARCH 08, 2017

Applies to:

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


Extending the OAM setup with and new oam managed server for clustering brings during managed server startup the error of the policy configuration are not be found.

The following exception are thrown

[2012-12-20T14:46:48.578+01:00] [oam22] [ERROR] [] [oracle.jps.policymgmt] [tid: Thread-55] [userId: ] [ecid: 0000Jis^6S29lZWVLyyGOA1GolQ7000002,1:28346] Get security module failed[[
  at oracle.security.jps.internal.policystore.entitymanager.impl.ConfigurationManagerImpl.getSecurityModule(ConfigurationManagerImpl.java:371)
  at oracle.security.jps.internal.policystore.distribution.FailoverUtil.getSecurityModule(FailoverUtil.java:129)
  at oracle.security.jps.internal.policystore.distribution.Distributor.distributePolicy(Distributor.java:130)
  at oracle.security.jps.internal.policystore.distribution.Distributor.run(Distributor.java:81)
  at java.lang.Thread.run(Thread.java:736)

[2012-12-20T14:46:48.583+01:00] [oam22] [WARNING] [] [oracle.jps.policymgmt] [tid: Thread-55] [userId: ] [ecid: 0000Jis^6S29lZWVLyyGOA1GolQ7000002,1:28346] The Security Module named OAM11goam22 does not exist!


Add an new OAM managed server. 


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