NAKACK/UNICAST: eager lock releasing not respected -------------------------------------------------- Key: JGRP-933 URL: https://jira.jboss.org/jira/browse/JGRP-933 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.9 In both NAKACK and UNICAST, we have atomic booleans, which are consulted before trying to acquire the lock. So if a lock is released eagerly in a ProtocolStack.down() call, although the lock is released, the atomic var isn't, and so subsequent threads will still not be able to process different messages. A simple solution would be to release the lock *and* the atomic var in down(). OTOH, we should see whether we can use either locks or atomic vars, but not *both*. This will need to be redesigned anyway with scopes in place (https://jira.jboss.org/jira/browse/JGRP-822). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira