[
https://issues.jboss.org/browse/ISPN-445?page=com.atlassian.jira.plugin.s...
]
Pedro Ruivo closed ISPN-445.
----------------------------
Resolution: Won't Fix
It won't be done for the following reasons:
* could make the stored data inconsistency if a thread advances without a lock.
* locks in JDK does not allow to steal them from other threads.
* full_xa + recovery allows a sysadmin to force a transaction rollback, releasing any
locks.
Ensure that locks time out
--------------------------
Key: ISPN-445
URL:
https://issues.jboss.org/browse/ISPN-445
Project: Infinispan
Issue Type: Feature Request
Components: Transactions
Reporter: Philippe Van Dyck
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 was sent by Atlassian JIRA
(v6.4.11#64026)