]
Manik Surtani updated ISPN-445:
-------------------------------
Fix Version/s: 5.2.0.FINAL
(was: 5.1.0.FINAL)
(was: 5.1.0.BETA3)
Ensure that locks time out
--------------------------
Key: ISPN-445
URL:
https://issues.jboss.org/browse/ISPN-445
Project: Infinispan
Issue Type: Feature Request
Components: Locking and Concurrency
Reporter: Philippe Van Dyck
Assignee: Manik Surtani
Fix For: 5.2.0.FINAL
When a lock is acquired, no mechanism ensure that it is reclaimed later.
So if for whatever reason the thread owning the lock is stuck in an endless loop or
waiting for some resource, the entry is locked. This kind of situation could happen in
cache stores trying to contact a remote storage.
The risk is quite high that other entries may be locked as well if you use lock stripping
(default : TRUE)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: