PM97238: nearCacheLastAccessTTLSyncEnabled property should not be required for a WXS dynamic cache near cache.

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

  • Attempting to start a WebSphere eXtreme Scale dynamic cache
    with a near cache currently requires the
    nearCacheLastAccessTTLSyncEnabled property set on the
    backingMap.   This should only be optional and should not
    result in the following warning:
    
    CWOBJ0006W:
    An
    exception
    occurred:
    com.ibm.websphere.objectgrid.ObjectGridRuntimeException:
    Dynamic cache near cache must have the
    nearCacheLastAccessTTLSyncEnabled backing map property set to
    true
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of Websphere eXtreme Scale        *
    *                  Version 8.6 or WebSphere XC10 DataPower     *
    *                  Appliance Version 2.5 using Dynamic Cache   *
    *                  with a near cache.                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: In eXtreme Scale 8.6 the                *
    *                      backingMap                              *
    *                      nearCacheLastAccessTTLSyncEnabled       *
    *                      should not be a required                *
    *                      property.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The nearCacheLastAccessTTLSyncEnabled feature will "touch" a
    remote cache entry whenever a "get" is performed on a
    corresponding near cache entry.   This is important if "Last
    Access" or "Least Recently Used" eviction is being performed
    on the remote dynamic cache data grid.   However, some
    users may be controlling their remote data grid size
    via invalidations (instead of Last Access or TTL eviction) and
    will want to avoid the overhead of the
    nearCacheLastAccessTTLSync processing.
    

Problem conclusion

  • For WebSphere eXtreme Scale, the
    nearCacheLastAccessTTLSyncEnabled property
    is
    now optional in the backingMap section of the Objectgrid.xml
    file.
    For the XC10 appliance, the custom property
    "com.ibm.websphere.xs.dynacache.disableNearCacheLastAccessTTLSyn
    c" can be set on the WAS dynamic cache instance, and
    this disables the LastAccessTTLSync function on the XC10.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM97238

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    860

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-09-17

  • Closed date

    2013-09-17

  • Last modified date

    2013-09-17

  • 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

  • R860 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere eXtreme Scale

Software version:

860

Reference #:

PM97238

Modified date:

2013-09-17

Translate my page

Machine Translation

Content navigation