[
https://jira.jboss.org/browse/ISPN-777?page=com.atlassian.jira.plugin.sys...
]
Mircea Markus commented on ISPN-777:
------------------------------------
Here is what is causing this. A and B two nodes.
- A start a remote lock acquisition on B and then fails
- there is a thread (T1) on B that tries to acquire a remote lock on behalf of A
- on A's leave, there is another thread that starts on B (T2) that tries to cleanup
all the unfinished transactions started by A
the problem is that T2 runs before T1. This way the lock is acquire and never released.
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