"lovelyliatroim" wrote : | | Now take sequence of events as follows | 1. Node A receives request for data item X | 2. Data Item X, not there, retrieve from source and place in cache. | 3. 14 mins later Node B is asked for data item X,it doesnt have it but node A does and is replicated on B via CCL. | 4. Data Item X is removed from the cache on node A because its 15 minute lifetime expectancy is up. | 5. Node A receives request for data item X,it doesnt have it but node B does. data Item is replicated on to A via CCL. So actually data item X is older than 15 minutes in reality. | | Can the above scenario happen? Will node A keep data Item X for another 15 mins and also have the possibility of the cycle continuing or does NODE B when it receives data Item X know that it must be evicted in 1 minutes time?? | | So does jboss cache replicate the timestamp of a data item if it is replicated from one node to another via CCL?? | | if not as a possible solution to achieve this could one write their own eviction policy and use an internal ID(member variable) that is transferred from node to node? | | This depends on which eviction policy you use. If you use the expiration policy, the expiry time is encoded as data on a node which means it will replicate to B and get evicted at the appropriate time. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147834#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...