[infinispan-issues] [JBoss JIRA] Updated: (ISPN-445) Ensure that locks time out

[Manik Surtani (JIRA)]

     [ https://jira.jboss.org/browse/ISPN-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manik Surtani updated ISPN-445:
-------------------------------

    Fix Version/s: 5.1.0.BETA1
                   5.1.0.Final
       Complexity: High


> Ensure that locks time out
> --------------------------
>
>                 Key: ISPN-445
>                 URL: https://jira.jboss.org/browse/ISPN-445
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Locking and Concurrency
>            Reporter: Phil vd
>            Assignee: Manik Surtani
>             Fix For: 5.1.0.BETA1, 5.1.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 contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira