Problem with Expiry Period for Multiple Caches in One Configuration File

Question

I need to have a Cache System with multiple expiry periods, i.e. few records should exist for, lets say, 1 hour, some for 3 hours and others for 6 hours. To achieve it, I am trying to define multiple caches in the config file. Based on the data, I choose the Cache (with appropriate expiry period). Thats where, I am facing this problem. I am able to create the caches in the config file. They have different eviction policies i.e. for Cache1, it is 1 hour and for Cache2, it is 3 Hours. However, the data that is stored in Cache1 is not expired after 1 hour. It expires after the expiry period of other cache i.e.e Cache2.
Plz correct me if I am not following the correct way of achieving the required. I am attaching the config file here.<br><br> <b> Attachment: </b><br>near-cache-config1.xml <br> (*To use this attachment you will need to rename 142.bin to near-cache-config1.xml after the download is complete.)

Answer 1

Hi Rajneesh,
In your cache mapping section, you have two wildcard mappings ("*"). These provide an ambiguous mapping for all cache names.
Rather than doing this, you should have a cache mapping for each cache scheme that you are using -- in your case the 1-hour and 3-hour schemes.
I would suggest removing one (or both) of the "*" mappings and adding entries along the lines of:
<pre>
<cache-mapping>
<cache-name>near-1hr-*</cache-name>
<scheme-name>default-near</scheme-name>
</cache-mapping>
<cache-mapping>
<cache-name>near-3hr-*</cache-name>
<scheme-name>default-away</scheme-name>
</cache-mapping>
</pre>
With this scheme, any cache that starts with "near-1hr-" (e.g. "near-1hr-Cache1") will have 1-hour expiry. And any cache that starts with "near-3hr-" will have 3-hour expiry. Or, to map your cache schemes on a per-cache basis, in your case you may replace "near-1hr-*" and "near-3hr-*" with Cache1 and Cache2 (respectively).
Jon Purdy
Tangosol, Inc.