IBM Support

PI10107: SLOW PERFORMANCE WHEN MANIPULATING EBAS AND CUS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Editing, browsing and manipulating EBAs and Composition Units
    is generally slow.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server OSGi Applications                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Working with EBAs and Composition       *
    *                      Units exhibits poor performance and     *
    *                      long delays.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    OSGi applications must parse the contents of EBA files for
    modules, configuration XML etc. when they are manipulated.
    This takes a long time.
    Objects created during parsing of the EBAs are not cached, but
    are often needed repeatedly while manipulating and working
    with EBAs and Compsition Units.
    The operations are also performed on a single thread.
    

Problem conclusion

  • This APAR introduces two new JVM custom properties.  When not
    set there is no change in behaviour.
    
    com.ibm.ws.eba.bla.proxies.archiveCacheSize (default 0,
    minimum 0, maximum 10000) - this property controls the size of
    a cache that is used for Archive objects parsed from an EBA.
    If an Archive is created, and the cache size is greater than
    0, it may be cached so that it can later be reused.  Typically
    a cache size of 500 is sufficient.  The cache is a soft cache
    and so its efficiency is affected by the amount of free heap
    space.
    
    com.ibm.ws.eba.bla.concurrency (default 1, minimum 1, maximum
    8) - this property controls the concurrency with which steps
    during the manipulation of EBAs might be performed.
    Typically, increasing this number from the default 1 will only
    have performance improvements if
    com.ibm.ws.eba.bla.proxies.archiveCacheSize is also set, and
    the EBAs being manipulated are sufficicently large in terms of
    the number of bundles.  Increasing the concurrency does not
    result in linear performance improvement because each thread
    requires its own Archive which is expensive to create.
    Consequently, a concurrency of two often offers the optimum
    performance.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.3.  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

    PI10107

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-01-22

  • Closed date

    2014-03-28

  • Last modified date

    2014-05-23

  • 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

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022