Sorry to take so long to reply -- I've been struggling to get a moment to look into this.
You're not missing anything; it seems the InvalidationManager invalidates the local cache whenever it processes an invalidation event. This behavior is necessary in one of the use cases for the cache invalidation framework, "Single JVM RO/RW Bean", where two versions of the same entity bean are deployed, one read-only, one read-write. (See Clustering docs for more on this usage.) This behavior ensures the RO bean will be invalidated after any update to the RW bean. Unfortunately, this behavior makes commit option A less useful in the more common CIF use case, invalidating remote caches of a clustered entity. I've opened a design discussion thread re: adding a config option to turn off the local cache invalidation. See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=77697. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3924839#3924839 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3924839 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
