PQ56429: MUST SET JAVA.LIBRARY.PATH IN JVM AND PATH SETTINGS IN ORDER FOR NATIVE CALLS TO FIND DLL FILES

 A fix is available

System Management Component Cumulative Fix for 4.0.2/4.0.3/4.0.4 /4.0.5



APAR status
Closed as program error.

Error description
Customer must set both the JAVA.LIBRARY.PATH in the JVM settings
and Path within the Environment tab, in order for the native
calls to find the needed .dll files.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users who are   *
*                 running native code within their application *
*                 servers, especially if their native DLLs     *
*                 load other DLLs.                             *
****************************************************************
* PROBLEM DESCRIPTION: Problems using JNI calls to load DLLs   *
*                      from a user's application when that or  *
*                      other applications within the server    *
*                      used resouces that also loaded DLLS.    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This problem is related to 
PQ52597.  Prior to 
PQ52597, if an
application server used resources (such as a data base) that
required native code, the java.library.path of the application
server was modified to include the paths to the resource's
dlls.  If the user also added PATH information to their DLLs
in the Environment config, this information was not getting put
in the java.library.path and their DLLs would not load.  This
was seen when trying to load native dlls from an application
installed in the Default Server.  After 
PQ52597, the
additional path information had to configured in both the
Environment and and JVM Settings windows.  Now, if the user
just needs to set the PATH, they only need to do it in the
Environment configuration.
Problem conclusion
The application server PATH and java.library.path were not
being set up properly prior to this fix.
Temporary fix
Efixes for 4.0.1 and 4.0.2 were provided to fix this problem.
Comments
APAR information
APAR number PQ56429
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-01-08
Closed date 2002-01-17
Last modified date 2002-01-17

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
ADMINSVR          

SRLS

Fix information
Fixed component name WEBSPHERE AE NT
Fixed component ID 5630A2201

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ56429
IBM Group: Software Group
Modified date: Jan 17, 2002