[jboss-user] [JBoss Cache: Core Edition] - Re: Cache modified time not updated in a clustered environme

manik.surtani@jboss.com do-not-reply at jboss.com
Wed Apr 2 06:09:02 EDT 2008

Evictions are local to each instance and timestamps are not replicated across a cluster.  This is because different instances in a cluster may access different nodes in the cache at different rates, so timestamps are only really relevant to a single cache instance.

What you can do is, if you know which node needs to be "kept alive" beyond the timeout, is to use:

  | TreeCache.getEvictionRegionManager().markNodeCurrentlyInUse(fqn, timeout)

This will prevent it from being evicted until the timeout or you call 

  | TreeCache.getEvictionRegionManager().unmarkNodeCurrentlyInUse(fqn)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140879#4140879

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140879

More information about the jboss-user mailing list