[JBPAPP-7500] JBoss Cache Region.deactivate can leave the entire cache locked with optimistic or pessimistic locking - JBoss Issue Tracker

XML

Word

Printable

Affects:

Release Notes
Release Notes Text:

Hide
Inactivating a JBoss Cache region locked the entire subtree of the region's parent and never unlocked it. Consequently, the cache became unusable because of the locks. Inactivating a region now only locks the parent, not the entire subtree of the parent. As a result, the cache is no longer locked after inactivation of a region.

Show
Inactivating a JBoss Cache region locked the entire subtree of the region's parent and never unlocked it. Consequently, the cache became unusable because of the locks. Inactivating a region now only locks the parent, not the entire subtree of the parent. As a result, the cache is no longer locked after inactivation of a region.
Release Notes Docs Status:
Documented as Resolved Issue
Docs QE Status:
NEW

A combination of https://issues.jboss.org/browse/JBCACHE-1608 and https://issues.jboss.org/browse/JBCACHE-1609
causes a JBoss Cache Region.deactivate call to lock the region's parent and all its children, and never unlock the children.

If the region is a child of the root, this can lock the entire cache.

This only affects pessimistic and optimistic locking. It does not affect MVCC.

is blocked by

JBCACHE-1607 LegacyRegionManagerImpl releases locks from other threads

JBCACHE-1609 LegacyRegionManagerImpl#inactivateRegion locks the parent's entire subtree

is related to

JBCACHE-1608 IdentityLock#releaseAll() is not recursive