IBM Support

PI12798: The catalog server can leak memory over time, which can cause out of memory errors.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When movement of the primary catalog occurs because of
    detected failures, and concurrent container failures are
    detected by the catalog server, this memory leak can be more
    prevalently seen.
    
    LockTimeoutException exception instances can take up a bulk of
    the memory because the exception messages contain the entire
    list of keys that are locked for particular transactions.
    

Local fix

  • TBD
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of WebSphere eXtreme Scale.       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Out of memory errors can occur in the   *
    *                      catalog server, especially in larger    *
    *                      topologies with numerous partitions.    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The cause of the memory leak had to do with a placement state
    that was not cleared correctly.  The logic was updated so
    that now the state is cleared correctly.
    Additionally, the LockTimeoutException exception class was
    updated to stop creating additional message text after a
    threshold is reached.  Now, when including the keys that
    are locked in a particular transaction in the exception
    message, only a subset of the keys that have been locked in
    the transaction are included, instead of including all of them
    if the number of keys is greater than the threshold.
    

Problem conclusion

  • An interim fix is available for this APAR.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI12798

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-02-28

  • Closed date

    2014-03-27

  • Last modified date

    2014-03-27

  • 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

    WS EXTREME SCAL

  • Fixed component ID

    5724X6702

Applicable component levels

  • R850 PSY

       UP

  • R860 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 March 2014