[ http://jira.jboss.com/jira/browse/JGRP-337?page=all ] Bela Ban updated JGRP-337: -------------------------- Fix Version/s: 2.6 (was: 2.5) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JGRP-337?page=comments#action_12358492 ] Vladimir Blagojevic commented on JGRP-337: ------------------------------------------ The following scenario could lead to a deadlock: - A and B - STOP_FLUSH is broadcast asynchronously - B receives STOP_FLUSH, broadcasts message M - A receives M, then its own STOP_FLUSH - In A: M blocks because latch hasn't yet been released: STOP_FLUSH is never delivered because (in the old stack) delivery for all msgs was FIFO (single queue) - With the concurrent stack, we can tag STOP_FLUSH as OOB, then it will be delivered concurrent to M -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira