Clustered Locks are not (always) Released upon Node Dying

Clone the following project:  https://github.com/radiosphere/infinispan-test Checkout the tag called the same as this issue ( ISPN-13537 ) Run the following commands (scripts are written on Ubuntu but should be fine on mac). Note that the two start-server commands should run in separate terminals. ./start-server.sh 8080 ./start-server.sh 8081 ./set-key.sh 8080 a 1 ./get-key.sh 8081 a (replies 1) ./kill-server.sh 8080 ./set-key.sh 8081 a 2 ./get-key.sh 8081 a (replies 1) Expected would have been that the last get-key would reply 2. Now for contrast you can run the following series: ./start-server.sh 8081 ./set-key.sh 8080 a 1 ./set-key.sh 8081 a 2 ./get-key.sh 8081 a (replies 1) ./kill-server.sh 8080 ./set-key.sh 8081 a 2 ./get-key.sh 8081 a (replies 2) It seems that trying (but failing) to acquire the lock makes the node react upon the lock owning node dying. This should preferably be done even if you didn't try to acquire the lock.