[infinispan-issues] [JBoss JIRA] Commented: (ISPN-777) Eager cluster wide locks not cleaned upon rollback

[Mircea Markus (JIRA)]

    [ https://jira.jboss.org/browse/ISPN-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564546#comment-12564546 ] 

Mircea Markus commented on ISPN-777:
------------------------------------

Bela suggested another solution at jgroups level:

#1 Keep track of the threads going into user space
#2 on up(VIEW): interrupt all of the threads in the list and wait for their return (time bounded)
This is similar to BARRIER (take a look)

13:09 mmarkus bela: yep, I think that should work. Do you need this in jgroups code base?

13:10 bela not necessarily somewhere in Infinispan would probably be better
This way, you can release this in lock-step with the ISPN release schedule
I would suggest you insert the protocol dynamically at config time, based on yoru config
e,g, if you don't run TXs, you won't need the protocol

13:11 mmarkus 13:11 bela: +1. I'll add this as an solution and have thought about it vs having the login in ISPN directly

> Eager cluster wide locks not cleaned upon rollback
> --------------------------------------------------
>
>                 Key: ISPN-777
>                 URL: https://jira.jboss.org/browse/ISPN-777
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Locking and Concurrency
>    Affects Versions: 4.2.0.BETA1
>            Reporter: Vladimir Blagojevic
>            Assignee: Mircea Markus
>            Priority: Blocker
>             Fix For: 4.2.0.CR1
>
>         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