[ https://issues.redhat.com/browse/ISPN-12364?page=com.atlassian.jira.plugi... ] Wolf-Dieter Fink updated ISPN-12364: ------------------------------------ Steps to Reproduce: * Start a 3 node cluster * try a lock on each node * stop one node   The behavior is expected to be the same with AVAILABLE and CONSISTENT reliability but it is different. With CONSISTENT the event is only fired for some locks With AVAILABLE the event is fired for all locks and the lock for the missing node is forced to release   reproducer code is here -> [https://github.com/wfink/infinispan.playground.lock] ensure pom will use the correct version and the mainClass is 'org.infinispan.wfink.playground.lock.ClusteredLockEmbeddedConfig' start 3 instance with exec:java and use the defined locks l1,l2,l3 each with a different node and stop one of them repeat the test after changed resources/infinispan.xml  reliablility attribute     was: * Start a 3 node cluster * try a lock on each node * stop one node   The behavior is expected to be the same with AVAILABLE and CONSISTENT reliability but it is different. With CONSISTENT the event is only fired for some locks With AVAILABLE the event is fired for all locks and the lock for the missing node is forced to release -- This message was sent by Atlassian Jira (v7.13.8#713008)