JBCACHE-923 is really a workaround to a flawed transaction manager implementation in WLS (TMs are not allowed to let more than one thread access a specific transaction at any given instant, according to the JTA spec), and IIRC you should not see a worker thread processing a transaction and a simultaneous commit or rollback on the same transaction, on a separate thread in WLS 10. Can you confirm that this is indeed the case, where a transactions acquires locks and due to a race between further processing and a rollback, the rollback doesn't properly happen and leaves stale/unreleased locks? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197703#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...