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 Cache provides a configuration option LockParentForChildInsertRemove. If this is set to false, insertions and removals of child nodes only require the acquisition of a read lock on the parent node.