[jbosscache-issues] [JBoss JIRA] (JBCACHE-1607) LegacyRegionManagerImpl releases locks from other threads
[
https://issues.jboss.org/browse/JBCACHE-1607?page=com.atlassian.jira.plug...
]
Dennis Reed updated JBCACHE-1607:
---------------------------------
Description:
LegacyRegionManagerImpl calls lockManager.unlockAll(NodeSPI) instead of
lockManager.unlockAll(NodeSPI, Owner owner).
This will cause it to remove any locks currently held by other threads.
Due to JBCACHE-1608 lockManager.unlockAll(NodeSPI) is broken, so the effects are limited
to the specific node.
was:
LegacyRegionManagerImpl calls lockManager.unlockAll(NodeSPI) instead of
lockManager.unlockAll(NodeSPI, Owner owner).
This will cause it to remove any locks currently held by other threads.
Due to JBCACHE- lockManager.unlockAll(NodeSPI) is broken, so the effects are limited to
the specific node.
LegacyRegionManagerImpl releases locks from other threads
---------------------------------------------------------
Key: JBCACHE-1607
URL: https://issues.jboss.org/browse/JBCACHE-1607
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Locking
Affects Versions: 3.2.8.GA
Reporter: Dennis Reed
Assignee: Dennis Reed
LegacyRegionManagerImpl calls lockManager.unlockAll(NodeSPI) instead of
lockManager.unlockAll(NodeSPI, Owner owner).
This will cause it to remove any locks currently held by other threads.
Due to JBCACHE-1608 lockManager.unlockAll(NodeSPI) is broken, so the effects are limited
to the specific node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira