We experienced a similar problem when we tried to access the same node that was modified again within the treecache listener (I do not know if that is the case with you). To our opinion the problem is that the lock and unlock interceptor use the thread as key for their lock table and not the method. This causes the problem that the lock table becomes empty but the node still maintains the lock. To solve the problem we changed the lock and unlock interceptors and made the method the key of the table. With this the problem went away.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3893003#3893003 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3893003 ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
