[infinispan-issues] [JBoss JIRA] Updated: (ISPN-518) Deadlock detection should be able to used with eager locking

[Manik Surtani (JIRA)]

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

Manik Surtani updated ISPN-518:
-------------------------------

         Assignee: Mircea Markus  (was: Manik Surtani)
    Fix Version/s: 4.1.0.CR1
                   4.1.0.Final


> Deadlock detection should be able to used with eager locking
> ------------------------------------------------------------
>
>                 Key: ISPN-518
>                 URL: https://jira.jboss.org/browse/ISPN-518
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Locking and Concurrency
>    Affects Versions: 4.1.0.BETA2
>            Reporter: Erik Salter
>            Assignee: Mircea Markus
>             Fix For: 4.1.0.CR1, 4.1.0.Final
>
>
> (As described on the forums):
> With a cache that explicitly (eagerly) locks a key and deadlock detecting -- 
> If transactions operating on a different node try to lock the same key, Infinispan will detect the deadlock.  However, it can't interrupt the deadlock, so the transaction ends up timing out.

-- 
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