After debugging and reading through the code, it seemed to me that jalapeno/cayenne JBC will always send an eviction on any put to the cache. The problem I am facing goes as follows:
I am using hibernate for persistence in a clustered environment. hibernate is running in side of a servlet container (SunONE to be specific). I planned on using JBC optimistically with asynchronous invalidations but when I run under this configuration I get the following problem: A loads X.v1 from the database. A sends invalidation(eviction) on put to local JBC (since B is empty no worries). A has warm cache B loads X.v1 from the database. B sends invalidation(eviction) on put to local JBC. B has warm cache A evicts X.v1 from cache and now has a cold cache even though the data has not changed. Is this a known issue/feature? I cant imagine we are the only organization that wishes to run under this configuration. Looking at the code it seems that the InvalidationInterceptor only operates in this way (sending evictions). I can send configs and such if need be. Thanks in advance, Keith. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991074#3991074 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991074 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
