weblogic.nodemanager. common.ConfigException Native version is enabled but node manager native library could not be loaded : NativeVersionEnabled

This post covers issue and fix while starting Node Manager .

Last week I encountered an error while starting Node Manager, error message reported was

weblogic.nodemanager.common.ConfigException: Native version is enabled but node manager native library could not be loaded

Caused by java.lang.UnsatisfiedLinkError no node manager in java.library.path

Quick Fix is to create/update $WL_HOME/common/ nodemanager/ nodemanager.properties (where nodemanager.properties is Node Manager’s properties file created on node manager’s successful start-up) with entry like

NativeVersionEnabled=false

NativeVersionEnabled when set to true (default value) uses native Node Manager Libraries are used for that operating system. As per Node Manager documentation, Native Node Manager Libraries are available only for Windows, Solaris, HP-UX, Linux (on Intel/Z-series), and AIX.

Note: Using native OS libraries improves system performance.

Other option is to define parameter LD_LIBRARY_PATH=$WL_HOME/server/native/<os> (Make sure that all required library files are in this directory)

About the Author Masroof Ahmad

Leave a Comment:

2 comments
Add Your Reply