[ http://jira.jboss.com/jira/browse/JBCACHE-19?page=comments#action_12310888 ] Bela Ban commented on JBCACHE-19: ---------------------------------
Simply calling remove() or removeData() doesn't work, because that would mean that these calls would be potentially replicated as well ! Have to introduce localRemove() and localRemoveDate() which locks but doesn't replicate > TreeCache.evict() doesn't go though interceptor chain > ----------------------------------------------------- > > Key: JBCACHE-19 > URL: http://jira.jboss.com/jira/browse/JBCACHE-19 > Project: JBoss Cache > Type: Bug > Versions: 1.2 > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 1.2.1 > > Original Estimate: 3 days > Remaining: 3 days > > When TreeCache.evict(0 is called, it calls _remove() or _removeData() > directly, and does *not* go through the interceptor chain. This means that no > locks are acquired. > Use case that fails (T-1 and T-2 are concurrent): > - Thread-1 calls put() > - Thread-2 calls evict() > - Thread-1 creates non-existing node /a/b/c > - Thread-2 deletes /a/b/c > - Thread-1 tries to lock /a/b/c, but fails > SOLUTION: evict() needs to call remove() or removeData() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
