[infinispan-issues] [JBoss JIRA] Updated: (ISPN-777) Race conditions in cleaning up stale locks held by dead members in a cluster

[Manik Surtani (JIRA)]

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

Manik Surtani updated ISPN-777:
-------------------------------

    Fix Version/s: 4.2.0.CR4
                       (was: 4.2.0.CR1)


> Race conditions in cleaning up stale locks held by dead members in a cluster
> ----------------------------------------------------------------------------
>
>                 Key: ISPN-777
>                 URL: https://issues.jboss.org/browse/ISPN-777
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Locking and Concurrency
>    Affects Versions: 4.2.0.BETA1
>            Reporter: Vladimir Blagojevic
>            Assignee: Manik Surtani
>            Priority: Blocker
>             Fix For: 4.2.0.CR4
>
>         Attachments: CacheScheduledCounter.java, ISPN-777_output.txt
>
>
> It seems that rollback sometimes does not release acquired eager locks. See attached test program and run two JVM instances on the same machine. Program schedules a task to run every 5 seconds. Tasks simply locks a key, gets the value, increases the value and puts it back surrounded by begin/commit/rollback tx boundary. 
> Steps to reproduce (keep repeating steps until problem is encountered):
> 1) Kill one running instance. 
> 2) Restart it
> See attached example output of a run. 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira