[jboss-user] [JBoss Cache: Core Edition] - Re: Pessimistic Locking
do-not-reply at jboss.com
Fri Feb 13 16:32:33 EST 2009
"nathanmesser" wrote :
| I have a transaction T1, which reads a node A from the cache, so it should have a read lock on the node.
| This transaction is then suspended, when an EJB method is called with it's transaction attribute set to requiresNew. This transaction T2 then writes to the node.
| Transaction T2 then commits, and transaction T1 continues, and commits as well.
| I'm using Pessimistic Locking with an Isolation Level of READ_COMMITTED
| Why does T1s read lock not block T2s obtaining of the write lock?
The semantic you described sounds like REPEATABLE_READ to me, not READ_COMMITTED.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210040#4210040
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210040
More information about the jboss-user