I know this. I don't understand why write lock persists AFTER replication is finished (if it was caused by replication). Because this lock (and read lock aquisition error!) exists till cache stop. I can try to read value 5 seconds later, 1 minute later, 1 day later - the node will still be locked.
Regards, Eugene View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3892225#3892225 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3892225 ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
