IBM Support

PM36144: APPLICATION INSTALL TAKES A LONG TIME WITH WEB CLIENT IN WAR WAR ANNOTATION SCANS INCLUDE NON-LIB JARS

Fixes are available

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.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
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

  • Deploying an application with a Java Web Start RCP GUI Client
    packaged within the WAR module under a folder external to the
    WEB-INF. The installation of the application takes over an hour
    to complete. If the application is built without the client
    packaged inside the deploy takes just a few minutes. It seems
    that WebSphere Application Server is scanning the JARs inside
    the webroot/client folder which is unexpected.
    -
    When processing JavaEE5 enabled web module archives, annotation
    processing incorrectly scans all jars of the web module archive.
    The WAR file annotation processing should only scan jars
    beneath the web module WEB-INF/lib directory.
    

Local fix

  • None
    Keywords: annotate annotation WCCM WCV
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0.                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: The time to install an application      *
    *                      takes a very long time.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The time to install an application takes a very long time when
    there is a large number of files packaged within the WAR
    module in a location external to the WEB-INF directory.
    When processing Java EE5 enabled web module archives,
    annotation
    processing incorrectly scans all jars of the web module
    archive.
    The WAR file annotation processing should only scan jars
    found beneath the web module WEB-INF/lib directory.
    

Problem conclusion

  • The annotation process has been modified to only scan jars
    beneath the web module WEB-INF/lib directory of a Java EE5
    enabled web module.
    
    A custom property has been defined to allow users to revert
    this change if necessary. The property name is
    "com.ibm.ws.amm.scan.disable.PM36144". Setting this property
    to "true" will cause all jars found in the webmodule to be
    scanned for annotations, which is the original (incorrect)
    behavior.
    A value of "false" will restrict annotation scanning to only
    jars found under the WEB-INF/lib path in the webmodule.
    The default value for this property is "false".
    If the property is set, an informational message will be
    displayed in the SystemOut.log file showing the value.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.21.  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

    PM36144

  • 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

    2011-04-01

  • Closed date

    2011-08-04

  • Last modified date

    2011-08-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 #: PM36144

Modified date: 04 August 2011