IBM Support

PH47936: INACTIVITY TIMEOUT VALUE LARGER THAN 2147483 SECONDS CAUSES IMMEDIATE CACHE INVALIDATION

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

  • Setting the Inactivity timeout in dynacache to a value larger
    than 2147483 seconds causes immediate cache invalidation.
    

Local fix

  • Either set Inactivity timeout to -1 (no timeout) or to a value
    of 2147483 seconds or less.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  V9.0 using a large inactivity timeout on    *
    *                  distributed map cache entries.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Cache entries are immediately           *
    *                      invalidated if the inactivity timeout   *
    *                      specified is larger than 2147483        *
    *                      seconds.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The inactivity timeout is specified in seconds and represented
    as
    a java int on the API.  The timeout is converted to milliseconds
    when dynacache sets the timer.  On large values, the conversion
    to milliseconds exceed the size of a java int and results in a
    negative value causing the cache entry to be immediately
    invalidated.
    

Problem conclusion

  • Internally, the timeout will now be represented by a java long
    and allow large timeout values when the seconds are converted
    to
    milliseconds.
    
    The fix for this APAR is targeted for inclusion in fix pack
    9.0.5.14 and 8.5.5.23. 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

    PH47936

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-07-12

  • Closed date

    2022-08-11

  • Last modified date

    2022-08-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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

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

Document Information

Modified date:
12 August 2022