REPEATABLE_READ extends to the scope of the TX. Inside TX1, once you have read 
/a/b, you are guaranteed that the value remains the same until you commit or 
roll back TX1. (We use R/W locks do implement this). So when TX1 commits in 
line 5, TX2 will be able to acquire the WL (upgrade from a RL) in line 6, on 
which it was blocked before TX1 committed because TX1 had the WL (and WLs are 
exclusive).
So the assert() on line 8 *must* show the value that TX2 modified if TX2's 
put() came before the assert().

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3895794#3895794

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3895794


-------------------------------------------------------
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

Reply via email to