Version:
WLS 10.3.6 and ADR 11.1.1.7.0 on Windows
Issue:
Getting errors when Managed Server was tried to start from weblogic console URL. Nodemanager was up and its status in console was Active. The same Managed Server can be started up using startManagedserver.cmd
Error:
<Nov 17, 2014 11:45:48 PM MST> <Warning> <Security> <BEA-090904> <The JPS or JRF jar is present in the classpath, but no system property supplied for "oracle.security.jps.config" and "oracle.domain.config.dir". The server will start without setting OPSS java policy provider.>
Nov 17, 2014 11:45:50 PM oracle.security.jps.internal.config.xml.XmlConfigurationFactory initDefaultConfiguration
SEVERE: java.io.FileNotFoundException: .\config\jps-config.xml (The system cannot find the file specified)
Nov 17, 2014 11:45:50 PM oracle.security.jps.internal.jaas.LoginConfigurationImpl <init>
SEVERE: .\config\jps-config.xml (The system cannot find the file specified)
oracle.security.jps.config.JpsConfigurationException: .\config\jps-config.xml (The system cannot find the file specified)
Reason:
Java Policy Store (JPS) configuration file (jps-config.xml ) is used to configure Policy, Credential, Key Store, Login Module and User Identity Store location.
When the Managed Server is started using WebLogic Console or Node Manager (NMStart) it uses nodemanager.properties file. This file has a parameter named StartScriptEnabled, which decides whether to use the startup scripts
StartScriptEnabled=false means NOT to use the startup scripts (startWebLogic or startManagedWebLogic) to start a server.
The startup scripts invoke setDomainEnv.sh that sets -Doracle.security.jps.config to location of $DOMAIN_HOME/config/fmwconfig/jps-config.xml.
Since in our case StartScriptEnabled was set to false, when invoked from nodemanager, it failed to load the jps config file.
Solution:
Set StartScriptEnabled=true in the nodemanager.properties file.
Restart the service
WLS 10.3.6 and ADR 11.1.1.7.0 on Windows
Issue:
Getting errors when Managed Server was tried to start from weblogic console URL. Nodemanager was up and its status in console was Active. The same Managed Server can be started up using startManagedserver.cmd
Error:
<Nov 17, 2014 11:45:48 PM MST> <Warning> <Security> <BEA-090904> <The JPS or JRF jar is present in the classpath, but no system property supplied for "oracle.security.jps.config" and "oracle.domain.config.dir". The server will start without setting OPSS java policy provider.>
Nov 17, 2014 11:45:50 PM oracle.security.jps.internal.config.xml.XmlConfigurationFactory initDefaultConfiguration
SEVERE: java.io.FileNotFoundException: .\config\jps-config.xml (The system cannot find the file specified)
Nov 17, 2014 11:45:50 PM oracle.security.jps.internal.jaas.LoginConfigurationImpl <init>
SEVERE: .\config\jps-config.xml (The system cannot find the file specified)
oracle.security.jps.config.JpsConfigurationException: .\config\jps-config.xml (The system cannot find the file specified)
Reason:
Java Policy Store (JPS) configuration file (jps-config.xml ) is used to configure Policy, Credential, Key Store, Login Module and User Identity Store location.
When the Managed Server is started using WebLogic Console or Node Manager (NMStart) it uses nodemanager.properties file. This file has a parameter named StartScriptEnabled, which decides whether to use the startup scripts
StartScriptEnabled=false means NOT to use the startup scripts (startWebLogic or startManagedWebLogic) to start a server.
The startup scripts invoke setDomainEnv.sh that sets -Doracle.security.jps.config to location of $DOMAIN_HOME/config/fmwconfig/jps-config.xml.
Since in our case StartScriptEnabled was set to false, when invoked from nodemanager, it failed to load the jps config file.
Solution:
Set StartScriptEnabled=true in the nodemanager.properties file.
Restart the service
Thanks
ReplyDelete