[
https://issues.jboss.org/browse/ISPN-3266?page=com.atlassian.jira.plugin....
]
William Burns updated ISPN-3266:
--------------------------------
Attachment: DistSyncL1PessimisticFuncTest.java
Attached test file that should work once pessimistic locking is fixed, where it acquires
lock in another thread blocked after doing so.
Pessimistic Force Write Lock doesn't acquire remote lock
--------------------------------------------------------
Key: ISPN-3266
URL:
https://issues.jboss.org/browse/ISPN-3266
Project: Infinispan
Issue Type: Bug
Components: Distributed Cache, Locking and Concurrency
Reporter: William Burns
Assignee: Mircea Markus
Attachments: DistSyncL1PessimisticFuncTest.java
Looking into FORCE_WRITE_LOCK it appears it only acquires a local lock in
PessimisticLockingInterceptor. Thinking about this, it seems this should acquire only a
remote lock on the primary node. Currently this isn't going to block writes at all.
I am guessing this was just an oversight when redoing the locking mechanism.
This causes other issues such as L1 inconsistencies which is how I ran into this and the
locking should only occur on the remote node.
--
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