[jboss-cvs] JBossCache/docs/JBossCache-UserGuide/en/modules ...
Brian Stansberry
brian.stansberry at jboss.com
Mon Feb 12 10:50:06 EST 2007
User: bstansberry
Date: 07/02/12 10:50:06
Modified: docs/JBossCache-UserGuide/en/modules
configuration_reference.xml transactions.xml
Log:
[JBCACHE-976] LockParentForChildInsertRemove default is false.
Revision Changes Path
1.11 +13 -0 JBossCache/docs/JBossCache-UserGuide/en/modules/configuration_reference.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: configuration_reference.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/docs/JBossCache-UserGuide/en/modules/configuration_reference.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- configuration_reference.xml 8 Feb 2007 14:53:01 -0000 1.10
+++ configuration_reference.xml 12 Feb 2007 15:50:06 -0000 1.11
@@ -349,6 +349,19 @@
<row>
<entry>
+ <para>LockParentForChildInsertRemove</para>
+ </entry>
+
+ <entry>
+ <para>Controls whether inserting or removing a node requires a write
+ lock on the node's parent (when pessimistic locking is used).
+ The default value is <code>false</code>.
+ </para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
<para>MultiplexerService</para>
</entry>
1.8 +6 -6 JBossCache/docs/JBossCache-UserGuide/en/modules/transactions.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: transactions.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/docs/JBossCache-UserGuide/en/modules/transactions.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- transactions.xml 30 Jan 2007 03:18:59 -0000 1.7
+++ transactions.xml 12 Feb 2007 15:50:06 -0000 1.8
@@ -146,13 +146,13 @@
<para>
By default, before inserting a new node into the tree or removing an existing node from the
- tree, JBoss Cache will attempt to acquire a write lock on the new node's parent node. This
- approach treats child nodes as an integral part of a parent node's state. This approach
- provide greater correctness, but at a cost of lesser concurrency if nodes are frequently
- added or removed. For use cases where this greater correctness is not meaningful, JBoss
+ tree, JBoss Cache will only attempt to acquire a read lock on the new node's parent node.
+ This approach does not treat child nodes as an integral part of a parent node's state.
+ This approach allows greater concurrency if nodes are frequently added or removed, but
+ at a cost of lesser correctness. For use cases where greater correctness is necessary, JBoss
Cache provides a configuration option <literal>LockParentForChildInsertRemove</literal>.
- If this is set to <literal>false</literal>, insertions and removals of child nodes only
- require the acquisition of a <emphasis>read lock</emphasis> on the parent node.
+ If this is set to <literal>true</literal>, insertions and removals of child nodes
+ require the acquisition of a <emphasis>write lock</emphasis> on the parent node.
</para>
</section>
</section>
More information about the jboss-cvs-commits
mailing list