IBM Support

PH63066: RESOURCE LEAKAGE: FILE HANDLES TO TRANLOG DIRECTORY

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 the transaction service is configured to be part of a
    Recovery Group and the file system is used to store the
    transaction service's recovery logs, the peer lease checking
    mechanism leaks filehandles resulting in increased memory
    usage and eventually the application server may terminate with a
    java.lang.OutOfMemoryError
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere Liberty Application Server        *
    *                  users of Transaction Service Recovery       *
    *                  Groups                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Recovery Groups for file system based   *
    *                      recovery logs, if configured, cause a   *
    *                      memory leak resulting in                *
    *                      java.lang.OutOfMemoryError              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Lease checking for transaction service 'Recovery Groups' for
    file system based transaction recovery logs does not close the
    instances of java.util.stream.Stream it uses when processing
    the leases.  This causes a memory leak and eventually memory
    exhaustion resulting in java.lang.OutOfMemoryError.
    This issue was caused by a regression introduced in 24.0.0.4
    by https://github.com/OpenLiberty/open-liberty/pull/27928
    

Problem conclusion

  • Lease checking for Recovery Groups was modified to
    correctly close the Streams it used when scanning leases for
    file system base recovery log.
    
    The fix for this APAR is targeted for inclusion in fix pack
    24.0.0.10. For more information, see 'Recommended Updates for
    WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH63066

  • Reported component name

    WAS LIBERTY COR

  • Reported component ID

    5725L2900

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-09-04

  • Closed date

    2024-10-11

  • Last modified date

    2024-10-11

  • 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

    WAS LIBERTY COR

  • Fixed component ID

    5725L2900

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
11 October 2024