"javax.security.jacc.policy.provider has been specified without enabling the SecurityManager." - WebLogic fails to startup if JAVA SE SecurityManager is disabled (Doc ID 1544543.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle WebLogic Server - Version 12.1.1.0 to 12.1.1.0 [Release 12c]
Java SE JDK and JRE - Version 7 to 7 [Release 7]
Information in this document applies to any platform.

Symptoms

WebLogic server instance fails to startup if JAVA SE SecurityManager is disabled.

An extract from <DOMAIN_HOME>/servers/AdminServer/logs/AdminServer.log

  ####<Jan 3, 2013 3:31:32 PM IST> <Critical> <WebLogicServer> <APIR-LAP> <AdminServer> <main> <<WLS Kernel>> <> <> <1357207292239> <BEA-000386> <Server subsystem failed. Reason:
  weblogic.security.SecurityInitializationException:[Security:090570]javax.security.jacc.policy.provider has been specified without enabling the SecurityManager.
  weblogic.security.SecurityInitializationException:[Security:090570]javax.security.jacc.policy.provider has been specified without enabling the SecurityManager.
   at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.checkJACCCmdlineForConsistency(CommonSecurityServiceManagerDelegateImpl.java:1751)
   at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1024)
   at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
   at weblogic.security.SecurityService.start(SecurityService.java:148)
   at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
   at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
   at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
  >

 
 

Cause

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