wrapper.java.library.path.append_system_path |
||||||||
The Java Service Wrapper includes a native library component,
and thus requires that the location of that library be specified
by passing its location to the JVM using the
java. Normally when Java is launched and a library path is not specified, the JVM will default to using the system PATH on Windows and the LD_LIBRARY_PATH on UNIX systems to locate any native libraries loaded by the application. This is akin to what happens with the CLASSPATH environment variable when a specific classpath is not specified when launching the JVM. The use of the CLASSPATH environment variable has fallen out of style because of all the conflict problems which can arise when multiple Java applications are installed on the same machine. The same issues are all there with the library path as well. But some applications still make use of the system PATH or LD_LIBRARY_PATH by default.
In general, it is advised that you avoid potential problems
when your application is deployed by being conservative about which directories
will be included in the Java library path.
However if there is a need to search the entire PATH,
then this property will cause the Wrapper to
append the contents of the system PATH
or LD_LIBRARY_PATH to the Java library path used to launch the JVM.
It is appended rather than prepended so that directories configured using the
wrapper.
NOTASome native libraries reference other dynamically linked libraries. Java will locate the initial JNI library using the Java library path, but the secondary libraries are loaded using the default mechanism for the platform. Please use the wrapper.system.library.path.<n> properties to configure paths were secondary libraries are located. |
Referencia: Librería |
|