IBM Support

PM14128: REMOTE INVALIDATION OF TRANSACTION-AWARE CACHES USING A FIRST LE VEL CACHE FAILS IN CLUSTER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using the first level cache in conjunction with
    transaction-aware caches, cache invalidations are not issued on
    remote servers of a WebSphere Portal cluster.
    In case of the 'com.ibm.wps.pe.portletentity' cache instance,
    this may lead to changes of portlet settings not being available
    across the servers in a cluster. In addition, a
    java.util.ConcurrentModificationException may be found in the
    log files, because servers access stale objects from the cache.
    

Local fix

  • A workaround is to disable the first level cache by setting the
    first level cache size of the cache in question to zero (0).
    For
    example, to disable the first level cache of the
    'com.ibm.wps.pe.portletentity' cache, add the following
    property
    to the WP CacheManagerService resource environment provider:
    cacheinstance.com.ibm.wps.pe.portletentity
    .firstLevelCacheSize=0
    
    Note: Disabling the first level cache may have a negative
    impact
    on the performance of the IBM WebSphere Portal environment.
    

Problem summary

  • When using the first level cache in conjunction with
    transaction-aware caches, cache invalidations are not issued on
    remote servers of a WebSphere Portal cluster.  In case of the
    'com.ibm.wps.pe.portletentity' cache instance, this may lead to
    changes of portlet settings not being available across the
    servers in a cluster. In addition, a
    java.util.ConcurrentModificationException may be found in the
    log files, because servers access stale objects from the cache.
    

Problem conclusion

  • The first level cache has been modified in that it also
    registers the invalidation listener on the underlying
    distributed map of a wrapped transaction-aware cache.
    
    Failing Module(s):
       Portlet Container
    
    Affected Users:
       All
    
    Version Information:
       Portal Version(s): 6.1.0.3
        Pre-Requisite(s): ---
         Co-Requisite(s): ---
    
    Manuel Steps:
       None
    
    Platform Specific:
       This fix applies to all platforms.
    
    PM14128 is part of Cumulative Fix 05 for Portal 6.1.0.3 /
    6.1.5.0.
    
    The Cumulative Fix is available from Fix Central:
    
    http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde
    r?apar=PM13061&productid=WebSphere%20Portal&brandid=5
    
    You may need to type or paste the complete address into your Web
    browser.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM14128

  • Reported component name

    WEBSPHERE PORTA

  • Reported component ID

    5724E7600

  • Reported release

    61C

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-05-10

  • Closed date

    2010-05-27

  • Last modified date

    2010-05-27

  • 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 PORTA

  • Fixed component ID

    5724E7600

Applicable component levels

  • R61C PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHRKX","label":"WebSphere Portal"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1.0.3","Line of Business":{"code":"LOB31","label":"WCE Watson Marketing and Commerce"}}]

Document Information

Modified date:
20 December 2021