[
https://issues.jboss.org/browse/ISPN-2549?page=com.atlassian.jira.plugin....
]
Dan Berindei updated ISPN-2549:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 5.3.0.Beta1
Resolution: Done
Invalidation mode caches with pessimistic transactions results in
stale remote locks
------------------------------------------------------------------------------------
Key: ISPN-2549
URL:
https://issues.jboss.org/browse/ISPN-2549
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta4
Reporter: Adrian Nistor
Assignee: Adrian Nistor
Fix For: 5.3.0.Beta1, 5.3.0.Final
Attachments: InvalidationModePessimisticLockingIssueTest.java
An invalidation mode cluster with two nodes A and B. Node A is coordinator.
Putting a key on node B results in a remote lock being acquired on A. But the lock on A
is not released when the TX commits. Subsequent attempts to lock the key on A will fail
with TimeoutException.
The key aspects to reproduce this are:
1. pessimistic locking
2. the transaction starts on a node different than the coordinator
This scenario does not involve any state transfer, so it should not be related to the
already known issues with stale locks caused by state-transfer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira