Caused by: java.lang.UnsatisfiedLinkError

Caused by: java.lang.UnsatisfiedLinkError

Caused by: java.lang.UnsatisfiedLinkError

Not able to start node manager with error Caused by: java.lang.UnsatisfiedLinkError –

ERROR 1:
weblogic.nodemanager.common.ConfigException: Native version is enabled but NodeManager native library could not be loaded
Caused by: java.lang.UnsatisfiedLinkError: no nodemanager in java.library.path
SOLUTION 1:
You would need to point your jmv to point to the native library nodemanager.dll file.
This can be done in two ways.
set LD_LIBRARY_PATH=%BEA_HOME%wlserverservenativewin32
set JAVA_OPTIONS=%JAVA_OPTIONS%; %LD_LIBRARY_PATH%;
or
set JAVA_OPTIONS=%JAVA_OPTIONS%;  -Djava.library.path=”C:OracleMiddlewareOracle_Homewlserverservernativewin32″
———————————————————————————
ERROR 2:
Caused by: java.lang.UnsatisfiedLinkError: C:OracleMiddlewareOracle_Homewlserverservernativewin32nodemanager.dll: Can’t load IA 32-bit .dll on a AMD 64 -bit platform
SOLUTION 2:
1.  Create a nodemanager folder under   <BEA_HOME> common folder if it’s a fresh installation as by default this folder is not created
2. Create a nodemanager.properties file under the created nodemanager folder and set the below property.
 NativeVersionEnabled=false
3. Start the NodeManager using the startNodeManager script.

For more such weblogic issues and resolution click here.

Latest Weblogic Interview Questions and Answers