The WebSphere® Application Server traces revealed an old
imsico.jar file loading from /usr/local/lib instead of the
/installedconnectors directory where the new IMS rar file is placed. The
old imsico.jar is in use by a Application Server V4.01. The /usr/local/lib
directory was not added to the Application Server V5 server classpath nor
was it in the IMS connector classpath. Directory /usr/local/lib is in the
native path of a CICS resource adapter. The old imsico.jar file was
removed from usr/local/lib from the CICS adapter, the server was recycled
and the problem was resolved.
Why is Application Server V5 loading all jars located in a native path
directory specified in a J2C resource adapter?
There is a misunderstanding about the design of the classloader, and an
assumption by some users that the native path directory is used to load
DLL files only (.so files for CICS); however, Application Server loads all
jars for use by ExtClassLoader.
DOC APAR PQ90038 documents Application Server classloader and resource
adapter path options in Versions 5.0 and 5.1.
|