Oracle Access Manager (OAM) Managed Server Startup Fails with java.security.AccessControlException
(Doc ID 2657712.1)
Last updated on JUNE 09, 2020
Applies to:Oracle Access Manager - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
The Oracle Access Manager (OAM) WebLogic managed server reaches a RUNNING state when started manuallyy, but the oam_server deployment is in listed in the WebLogic Server (WLS) console with a "Failed" state and the OAM managed server is not functional. The system output for the OAM managed server startup (either the $DOMAIN_HOME/servers/<SERVER NAME>/logs/<SERVER NAME>.out if started via node manager, nohup output, or terminal output if started interactively) shows the following errors:
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