If you install an adapter that includes native path elements, consider
the following: If you have more than one native path element, and one of the
native libraries (native library A) is dependent on another library (native
library B), then you must copy native library B to a system directory. Because
of limitations on most UNIX systems, an attempt to load a native library does
not look in the current directory.
After you create and save the connection
factories, you can modify the resource references defined in various modules
of the application and specify the Java Naming and Directory Interface (JNDI)
names of the connection factories wherever appropriate.
Note: A given
native library can only be loaded one time for each instance of the Java virtual
machine (JVM). Because each application has its own classloader, separate
applications with embedded RAR files cannot both use the same native library.
The second application receives an exception when it tries to load the library.
If
any application deployed on the application server uses an embedded RAR file
that includes native path elements, then you must always ensure that you shut
down the application server cleanly, with no outstanding transactions. If
the application server does not shut down cleanly it performs recovery upon
server restart and loads any required RAR files and native libraries. On completion
of recovery, do not attempt any application-related work. Shut down the server
and restart it. No further recovery is attempted by the application server
on this restart, and normal application processing can proceed.