[jboss-user] [JBossCache] - Re: Exclusive lock on bottom (leaf) node only?
http://jira.jboss.com/jira/browse/JBCACHE-1102 View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4053364#4053364 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4053364 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: Exclusive lock on bottom (leaf) node only?
Great stuff! View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4053461#4053461 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4053461 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: Exclusive lock on bottom (leaf) node only?
What is the status of this? Should Option.setForceWriteLock() write-lock all nodes all the way up from the designated node or not? If this is in fact correct behaviour, is there any recommended way of solving the leaf-only locking scenario described in this thread? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4053086#4053086 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4053086 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: Exclusive lock on bottom (leaf) node only?
The option should not force WLs all the way to the leaf - it should only be forced on the leaf. Will create a JIRA for this shortly. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4053087#4053087 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4053087 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: Exclusive lock on bottom (leaf) node only?
REPEATABLE_READ View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4050151#4050151 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4050151 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: Exclusive lock on bottom (leaf) node only?
Using repeatable read as transaction isolation will not stop concurrent read access to the node if i'm not mistaken. My interpretation is that atijms want to get an exclusive lock on '/a/b/n1' regardless of read or write operation. If this is correct then repeatable_read would not solve the issue. I have actually the same requirement, I need to access a node and lock that node (and that node only) excusively. I do not want to write-lock the parent nodes. If I use Option.setForceWriteLock() , then all nodes are write locked. So far, I have found two working solutions, none which are pretty imho. 1. Perform a write operation such as remove(...) first when accessing the node. That acquires a write lock during the transaction right away. Not very performance wise I would gather though =) 2. Make your own locking scheme. I implemented this, it doesn't feel right (feels like a true hack), but it works for me. First I get the lock from the node, add the lock to my transaction. Then I acquireAll on the node for read locks and finally acquire write lock on the leaf node only. I'd be real happy if there was an option we could provide (similar to Options.setForceWriteLock()) that let us readlock the branch and write lock the leaf node only... View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4050321#4050321 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4050321 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: Exclusive lock on bottom (leaf) node only?
anonymous wrote : | My interpretation is that atijms want to get an exclusive lock on '/a/b/n1' regardless of read or write operation. If this is correct then repeatable_read would not solve the issue. | Yes, if this is the case then R_R won't help. Option.setForceWriteLock() should only acquire a WL on the target node (leaf). If it does so for every parent node as well, then this is a bug. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4050334#4050334 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4050334 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: Exclusive lock on bottom (leaf) node only?
The use case you describe sounds like what IIRC Option.forceWriteLock was meant for; kind of a SELECT FOR UPDATE semantic. Not sure if it needs to lock all the nodes on the way down (it definitely does). I'd think not for the usages I've thought about, but haven't thought about it hard. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4050357#4050357 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4050357 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: Exclusive lock on bottom (leaf) node only?
Oops, Manik, I didn't see your post. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4050360#4050360 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4050360 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
