IBM Support

PI88192: Map entries do not expire at the right time after an update operation.

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

  • Map entries get the wrong expiration time when using
    ObjectMap.setTimeToLive() with an update operation.  When this
    happens  entries stay in the grid longer than intended causing
    a memory leak.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of eXtreme Scale who use time to      *
    *                  live eviction function and use the          *
    *                  ObjectMap.setTimeToLive() API to override   *
    *                  the default time to live.  Users of         *
    *                  eXtreme Scale who use the HTTP session      *
    *                  replication function are also affected.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Map entries do not expire at the time   *
    *                      that they were configured to when the   *
    *                      timeout is overriden with an update     *
    *                      operation.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When processing update operations where the user overrides the
    time to live for the entry, the precision of the timeout
    value that is flowed from client to server is not correctly
    processed.  This miscalculation causes the timeout that is
    used to determine the expiration time to be larger than it is
    supposed to be.  The calculation for the expiration time was
    updated to use the right value for the timeout.
    

Problem conclusion

  • An interim fix is available for this APAR on fix central for
    the 8.6.1.2 release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI88192

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    860

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-09-30

  • Closed date

    2017-10-10

  • Last modified date

    2017-10-10

  • 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

  • R861 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":"860","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 October 2017