Actually, I have a possible bug to report. I thought I'd check here first. The bug occurs when using TreeCacheAOP.
I put an object into the cache, which is then replicated to other nodes. This all works fine. One node then calls removeObject(), which removes the FQN and cache interceptor on the local cache instance. The remove operations are replicated on the other nodes, but the cache interceptors are not removed from their objects. Therefore, if another node uses the object, the cache simply assumes that the object was evicted and re-creates it, which re-replicates it! I'm assuming that the fix just involves TreeCacheAOP overriding _remove() and doing something appropriate. Should I raise a JIRA issue for this, or have I just missed something obvious? Tim. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3877583#3877583 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3877583 ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
