My Oracle Support Banner

OPSS - Admin server not coming up with JPS errors such as JPS-04001, JPS-01051, JPS-00054 (Doc ID 2478475.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Platform Security for Java - Version 11.1.1.9.0 and later
Information in this document applies to any platform.

Symptoms

Admin server not coming up observinf the next errors:

 

#### <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <>
#### <> <> <> weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-04001: Cannot read the default policy store.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:888)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:263)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: oracle.security.jps.JpsRuntimeException: JPS-04001: Cannot read the default policy store
.......................

Caused By: java.lang.RuntimeException: There was an internal error in the policy store.
......................

Caused By: oracle.security.jps.JpsRuntimeException: JPS-04001: Cannot read the default policy store.
.....................
Caused By: oracle.security.jps.JpsException: java.security.PrivilegedActionException: oracle.security.jps.service.idstore.IdentityStoreException: JPS-01051: Credential audit events cannot be logged. Reason oracle.security.jps.service.audit.AuditException: JPS-00054: Failed to create the auditor for JPS.
...................
Caused By: java.security.PrivilegedActionException: oracle.security.jps.service.idstore.IdentityStoreException: JPS-01051: Credential audit events cannot be logged. Reason oracle.security.jps.service.audit.AuditException: JPS-00054: Failed to create the auditor for JPS.
.....................

Caused By: oracle.security.jps.service.idstore.IdentityStoreException: JPS-01051: Credential audit events cannot be logged. Reason oracle.security.jps.service.audit.AuditException: JPS-00054: Failed to create the auditor for JPS.
.....................

Caused By: oracle.security.jps.service.credstore.CredStoreException: JPS-01051: Credential audit events cannot be logged. Reason oracle.security.jps.service.audit.AuditException: JPS-00054: Failed to create the auditor for JPS.
.......................

Caused By: oracle.security.jps.service.audit.AuditException: JPS-00054: Failed to create the auditor for JPS.

.......................
Caused By: oracle.security.jps.JpsException: JPS-08511: Audit store was not fully initialized until data source is available.
.....................



Changes

 Issue happened after doing refresh activity, when pointing to DR OAM installation, then Admin server is not starting.

Cause

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
Symptoms
Changes
Cause
Solution
References


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