PM19152: ARCHIVE CLASSLOADING DOES NOT FULLY TRAVERSE DEPENDENT ARCHIVES

Fixes are available

APAR status

Closed as program error.

Error description

Internal tooling, through the implementation class
ArchiveFileDynamicClassloader, provides two independent APIs
for performing resource lookup, which should use the fully
expanded class search path.  One API works through
'ArchiveFileDynamicClassloader.loadClass', correctly processes
the class search path.  A second API which works through
'ArchiveFileDynamicClassLoader.getResource', fails to
fully expand the class search path.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0                                 *
****************************************************************
* PROBLEM DESCRIPTION: Enterprise Application module class     *
*                      loading does not fully traverse         *
*                      dependency archives                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
IBM WebSphere Application Server internal code paths make use
of an API on Enterprise Application module class loaders which
is not fully enabled to scan the dependency class path of the
module.  That leads to cases where class references fail to
resolve.
The IBM WebSphere Process Server encounters the problem when
using 'ArchiveFileDynamicClassLoader.getResource(String)'.
More specifically, modules have a class loader dependency on
three sets of archives which are present as elements of an
Enterprise Application (EAR).  The three sets of archives are,
first, archives listed in the manifest class path of the
module, second, archives present in the application library
directory, and third, other simple java archives which are
children of the application.
The problem is that when scanning for resources in these three
types of dependency archives, the scan does a simple lookup of
the resource in each dependency archive, but does not chain to
archives listed as dependency archives in the manifest class
path of each dependency archive.

Problem conclusion

The code was updated to allow full traversal of dependency
archives to be enabled as a caller enabled option.  (The code
update triggers only if specifically enabled.  The default
behavior is to continue to do only simple lookups in the
dependency archives.  The new function cannot be enabled as
new default behavior because this could result in changes in
what classes are loaded from the module class loader,
potentially leading to changed application behavior.)

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.13 and 8.0.0.4.  Please refer to the Recommended
Updates


page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM19152
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-07-23
Closed date
2012-03-28
Last modified date
2012-03-28

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PM19152: ARCHIVE CLASSLOADING DOES NOT FULLY TRAVERSE DEPENDENT ARCHIVES

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?