Configuring the near cache to update the LAST_ACCESS_TIMEvalue for the TTL evictor in the data grid

You can configure the near cache configured on the client to propagate time-to-live (TTL) read operations to the remote data grid. Configuring this propagation prevents cache entries from getting prematurely evicted from the remote data grid.

1. Set the nearCacheLastAccessTTLSyncEnabled attribute in the ObjectGrid descriptor XML file.
   Set this attribute on the same backingMap element on which you have the TTL evictor enabled. For more information, see ObjectGrid descriptor XML file.

   nearCacheLastAccessTTLSyncEnabled

   Set the value to true to enable time-to-live (TTL) information to be synchronized with the remote data grid. To enable a near cache for a dynamic cache instance, this value must be set to true. If you are not using a dynamic cache near cache, you must enable the LAST_ACCESS_TIME TTL evictor type when you enable this property.

   Attention: Setting the value to true for a dynamic cache near cache is now optional.

   Default: false (Optional)

   In the following example, both maps in the Grid ObjectGrid element have a TTL evictor configured. The Map1 backingMap element also has synchronization with the remote data grid enabled.

   <?xml version="1.0" encoding="UTF-8"?>
   <objectGridConfig xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://ibm.com/ws/objectgrid/config ../objectGrid.xsd"
    xmlns="http://ibm.com/ws/objectgrid/config">
       <objectGrids>
           <objectGrid name="Grid">         
                <backingMap name="Map1" lockStrategy="OPTIMISTIC" nearCacheLastAccessTTLSyncEnabled="true"  
   							ttlEvictorType="LAST_ACCESS_TIME" timeToLive="60"  copyMode="COPY_TO_BYTES"/>
                <backingMap name="Map2" lockStrategy="OPTIMISTIC" nearCacheLastAccessTTLSyncEnabled="false" 
   							ttlEvictorType="LAST_ACCESS_TIME" timeToLive="60" copyMode="COPY_TO_BYTES"/>
           </objectGrid>
       </objectGrids>
   ...
   ...
   </objectGridConfig>

2. Restart the container servers and clients.
   For more information, see Starting and stopping stand-alone servers and Configuring container servers in WebSphere Application Server.