Node Manager Fails With Wrong ELF class: ELFCLASS64 and WLST Startserver Fails With java.io.FileNotFoundException jps-config.xml
(Doc ID 1204606.1)
Last updated on SEPTEMBER 01, 2023
Applies to:
Oracle WebCenter Portal - Version 11.1.1.5.0 and laterInformation in this document applies to any platform.
Symptoms
On 64 bit Machine (Linux or Solaris), the following error occurs when trying to start Node Manager from WLST:
java weblogic.WLST
wls:/offline> startNodeManager()
Launching NodeManager .....
NMProcess: <Sep 2, 2010 11:02:33 AM> <SEVERE> <Fatal error in node manager server>
NMProcess: weblogic.nodemanager.common.ConfigException: Native version is enabled but nodemanager native library could not be loaded
NMProcess: at weblogic.nodemanager.server.NMServerConfig.initProcessControl(NMServerConfig.java:245)
NMProcess: at weblogic.nodemanager.server.NMServerConfig.<init>(NMServerConfig.java:185)
NMProcess: at weblogic.nodemanager.server.NMServer.init(NMServer.java:181)
NMProcess: at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:147)
NMProcess: at weblogic.nodemanager.server.NMServer.main(NMServer.java:353)
NMProcess: at weblogic.NodeManager.main(NodeManager.java:31)
NMProcess: Caused by: java.lang.UnsatisfiedLinkError: /<FMW_HOME>/wlserver_10.3/server/native/solaris/sparc64/libnodemanager.so: ld.so.1: java: fatal: /<FMW_HOME>/wlserver_10.3/server/native/solaris/sparc64/libnodemanager.so: wrong ELF class: ELFCLASS64 (Possible cause: architecture word width mismatch)
NMProcess: at java.lang.ClassLoader$NativeLibrary.load(Native Method)
NMProcess: at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1758)
NMProcess: at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1683)
NMProcess: at java.lang.Runtime.loadLibrary0(Runtime.java:823)
NMProcess: at java.lang.System.loadLibrary(System.java:1028)
NMProcess: at weblogic.nodemanager.util.UnixProcessControl.<init>(UnixProcessControl.java:24)
NMProcess: at weblogic.nodemanager.util.Platform.getProcessControl(Platform.java:114)
NMProcess: at weblogic.nodemanager.server.NMServerConfig.initProcessControl(NMServerConfig.java:243)
NMProcess: ... 5 more
NMProcess:
NMProcess: Sep 2, 2010 11:02:33 AM weblogic.nodemanager.server.NMServer main
NMProcess: SEVERE: Fatal error in node manager server
NMProcess: weblogic.nodemanager.common.ConfigException: Native version is enabled but nodemanager native library could not be loaded
NMProcess: at weblogic.nodemanager.server.NMServerConfig.initProcessControl(NMServerConfig.java:245)
The other error occurs when trying to start the Admin Server or Managed Server from WLST using "startServer" Node Manager command:
java weblogic.WLST
wls:/offline> startServer('AdminServer','WCDomain','t3://<HOSTNAME>:7001','weblogic','<PASSWORD>','/<WCP_DOMAIN>')
WLST-WLS-1280781434135: Aug 2, 2010 4:37:41 PM oracle.security.jps.internal.config.xml.XmlConfigurationFactory initDefaultConfiguration
WLST-WLS-1280781434135: SEVERE: java.io.FileNotFoundException: <WCP_DOMAIN>/config/fmwconfig/./config/jps-config.xml (No such file or directory)
WLST-WLS-1280781434135: <Aug 2, 2010 4:37:41 PM EDT> <Error> <Security> <BEA-090892> <The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider>
Changes
This is a 64 bit Machine
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 |