Is the issue raised in JBCACHE-923 likely to be an issue with Weblogic using MVCC locking? We're using Weblogic 10.3 We're currently seeing a situation, after a transaction timed out while making a lot of modifications to our cache, where a particular node in the cache is locked. The behaviour we're seeing sounds very similiar to the issue raised in JBCACHE-923, and as the last comment mentions that it was hoped to address this issue more fully with MVCC locking, I wondered if the situation could still occur? We are using synchronous replication in a cluster, and haven't yet seen this issue in a single instance, if that's relevant. Also, is it possible to put a timeout on locks in JBoss cache, so that if this situation occurs, and a lock is left after a transaction has rolledback, the lock will eventually be released? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197693#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...