"drcallaway" wrote : "galder.zamarreno(a)jboss.com" wrote : | | What do you exactly mean with data changing? Is data changing as a result of your interaction with the cache? Are you changing the data directly in the cache store? I don't understand why you'd want the data to be replaced with the one in the cache store. | | I mean that the data is changed by another cache client. For example, say I store pricing information in my cache that changes once a month. I can refresh the cache from a single client by replacing the existing "pricing" node with new information and this will push the new information into the backing database. However, all of the other clients that share this database aren't aware that the data has changed. I'd like to be able to force a refresh periodically so that these other clients dump their current information and reload from the data store. Looks to me the different caches accessed by your clients are not clustered which is the root of your problem. If they're clustered, modifications could be replicated to other cache instances or modifications could result in invalidation messages to other nodes. Either of these two options would allow other clients to access the most up to date data. In the case of replication because the cache contains up to date data. In the case of invalidation because after data was updated in another node, the cache would not contain the data and it will result on the cache store being queried. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239045#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...