IBM Support

PK93206: JAR FILES MAY BE MISSING FROM THE CLASSPATH OF JAVAEE 5 APPLICATIONS

Fixes are available

7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The manifest Class-Path entries of a jar located in the
    library-directory (whether the default 'lib' or another) are not
    visible to the application and WAR classpath.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Application and module class path       *
    *                      entries do not include manifest         *
    *                      class path entries for library          *
    *                      directory java archives.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An application or module processed by the IBM WebSphere
    Application Server has a class path which includes entries for
    java archives (JAR files) in the application library directory.
    
    Current behavior is to not expand manifest class path entries
    of java archives in the application library directory.
    
    This APAR adds three entry points which allow the manifest
    class path entries to be expanded.
    
    This APAR updates server runtime class path graph code to use
    the new API to obtain a dependency class path which has
    expanded library directory manifest class path entries.
    
    In detail:
    
    An application or module has a class path which is made
    available through several programming interfaces (APIs).  The
    following APIs are of note:
    
    org.eclipse.jst.j2ee.commonarchivecore.internal.Archive:
      public RuntimeClasspathEntry[] getFullRuntimeClassPath();
      public RuntimeClasspathEntry[] getLocalRuntimeClassPath();
      public RuntimeClasspathEntry[] getDependencyClassPath();
    
    The behavior of these API's is as follows:
    
    Full runtime class path:
    
    The full runtime class path is the local runtime class path
    concatenated with the dependency class path.
    
    Local runtime class path:
    
    For non-WAR modules, the singleton containing the binaries
    path of the module.
    
    For WAR modules, the module binaries WEB-INF/classes
    directory, concatenated of all java archives under the
    WEB-INF/lib directory, plus the binaries path of the
    module.
    
    The local runtime class path does not expand manifest
    entries of java archives.
    
    Dependency class path:
    
    The concatenation of all java archives in the application
    library directory (for which the manifest entries are not
    expanded) with the java archives listed in the manifest class
    path (for which manifest entries are expanded).
    
    For backwards compatibility, these existing APIs are
    unchanged.  For this APAR, two constants and three API entry
    points were added:
    
    org.eclipse.jst.j2ee.commonarchivecore.internal.Archive:
    
      public static final boolean DO_EXPAND_LIB_ENTRIES;
      public static final boolean DO_NOT_EXPAND_LIB_ENTRIES;
    
      public List<RuntimeClasspathEntry>
    getFullRuntimeClassPath(boolean expandLibEntries);
      public List<RuntimeClasspathEntry>
    getDependencyClassPath(boolean expandLibEntries);
      public List<RuntimeClasspathEntry>
    getLibraryDirectoryClassPath(Application appDDOverride,
    boolean expand);
    
    The behavior of the new API entry points is according to the
    'expandLibEntries' or 'expand' parameter.  If the parameter
    value is DO_NOT_EXPAND_LIB_ENTRIES (false), the behavior is the
    same as for the CORRESPONDING pre-APAR API entry points.  If
    the parameter value is DO_EXPAND_LIB_ENTRIES (true), the
    behavior is altered, such that expansion is performed on the
    manifest class path entries of java archives in the library
    directory.
    

Problem conclusion

  • This APAR adds three entry points which allow the manifest
    class path entries to be expanded.  Also, this APAR updates
    server runtime class path graph code to use the new API to
    obtain a dependency class path which has expanded library
    directory manifest class path entries.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.9.  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

    PK93206

  • 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

    2009-08-05

  • Closed date

    2010-01-04

  • Last modified date

    2010-01-04

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PK93206

Modified date: 04 January 2010