IBM Support

PM09564: SLOW APPLICATION DEPLOYMENT RESULTING FROM ZIP FILE DECOMPRESSION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Slow application deployment resulting from zip file
    decompression.  The following thread was found to be the major
    contributor to the slow deployment:
    
    "WebContainer : " daemon prio= tid= nid=
    
    runnable []
        at java.util.zip.Inflater.inflateBytes(Native Method)
        at java.util.zip.Inflater.inflate(Inflater.java:215)
        - locked <> (a java.util.zip.Inflater)
        at
    java.util.zip.InflaterInputStream.read(InflaterInputStream.java:
    128)
        at
    java.util.zip.ZipInputStream.read(ZipInputStream.java:139)
        at
    java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:91)
        at
    java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:69
    )
        at
    org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.NestedA
    rchiveLo
    adStrategyImpl.getZipInputStreamSkippedTo(NestedArchiveLoadStrat
    egyImpl.
    java:209)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Slow application deployment resulting   *
    *                      from zip file                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Application deployment becomes very slow when it contains
    nested jar/zip files.
    

Problem conclusion

  • Obtaining input streams from nested archives is expensive
    because the archive must be decompressed.  By expanding the
    file to temporary storage this overhead can be avoided and
    performance improved.
    
    To disable this feature, use the following custom JVM property
    setting:
    
    com.ibm.config.eclipse.wtp.dynamic.expansion=false
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.1.0.33.  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

    PM09564

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    61S

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-03-10

  • Closed date

    2010-05-04

  • Last modified date

    2010-05-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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

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

Document Information

Modified date:
24 October 2021