IBM Support

PI92239: CLIENT CANNOT UNMOUNT TRANLOG DIRECTORY AFTER CALLING DISABLEMEMBER ON HAMANAGER MBEAN WHEN USING MEMORY-MAPPED FILES.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Calling HAManager MBean method disableMember does not result
    in the release of the transaction service log files when the
    transaction service is using memory-mapped files.
    This is the case regardless of how many times garbage
    collection is performed, the files will continue to be
    referenced.
    
    As a result, they can not un-mount the TRANLOG directory.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: The transaction service log directory   *
    *                      for an HA enabled application server    *
    *                      cannot be un-mounted after calling      *
    *                      disableMember.                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Calling the HAManager MBean disableMember method for an
    application server both disables and deactivates the member.
    If peer recovery has been performed the disableMember request
    correctly results in the log files being closed by the peer,
    however the peer retains an object reference to the file.  If
    the transaction service is using memory-mapping for the log
    files then this prevents the directory containing the logs
    from being un-mounted.
    

Problem conclusion

  • The recovery log service was modified so that it no longer
    retains the object references to the log files after it has
    finished performing peer recovery.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.5.14 and 9.0.0.8.  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

    PI92239

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-09

  • Closed date

    2018-05-15

  • Last modified date

    2018-05-15

  • 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

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
18 October 2021