"pr3ston" wrote : | Is there any way to lock a node on modification? |
The short answer is no. It is upon replication that other caches in the cluster are considered in the tx. "pr3ston" wrote : | Is there any other way to lock a node across the cluster and then release it? Do you have any recommendations on an open source transaction manager that we can use to achieve this? | Unfortunately no. Distributed locks are created during the prepare phase and are released after commit or rollback, just like any distributed transaction manager would handle it. This is pretty much how distributed transactions work. With JBossCache 1.3 we will be releasing optimistic node locking (see [http://wiki.jboss.org/wiki/Wiki.jsp?page=OptimisticNodeLocking]) which may be able to help though. This is also available in 1.2.4 as alpha quality... "pr3ston" wrote : | Thank you for your help. | No probs! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3905543#3905543 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3905543 ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
