[ https://issues.jboss.org/browse/JGRP-2234?page=com.atlassian.jira.plugin.... ] Bram Klein Gunnewiek edited comment on JGRP-2234 at 2/9/18 4:39 AM: -------------------------------------------------------------------- [~belaban] Thanks for resolving this! Using the testcase provided is fine obviously. A side note about the "multiple members holding the same lock in a split brain": since JGroups can't prevent these scenario's I would suggest that in case of "multiple lock holders" the lock should be released again when *all* lock holders have released it. E.G. in a cluster of [A,B,C,D] that splits into [A,B][C,D] where A and C hold the same lock (lock X) and they merge back into one cluster [A,B,C,D] I think think lock X should be 'released' after both A and C unlock it. But that might be something to think about in JGRP-2249. was (Author: bramklg): [~belaban] Thanks for resolving this! Using the testcase provided is fine obviously. A side note about the "multiple members holding the same lock in a split brain": since JGroups can't prevent these scenario's I would suggest that in case of "multiple lock holders" the lock should be released again when *all* lock owners have released it. E.G. in a cluster of [A,B,C,D] that splits into [A,B][C,D] where A and C hold the same lock (lock X) and they merge back into one cluster [A,B,C,D] I think think lock X should be 'released' after both A and C unlock it. But that might be something to think about in JGRP-2249. -- This message was sent by Atlassian JIRA (v7.5.0#75005)