[
https://jira.jboss.org/jira/browse/JGRP-1079?page=com.atlassian.jira.plug...
]
Bela Ban commented on JGRP-1079:
--------------------------------
We also need to check for this flag in the regular removal look (after removeMany()): if
we have OOB messages in the xmit_table, but the next message is *not* OOB, then we would
simply discard the OOB message !
OOB messages are discarded when pool size is small and
rejection_policy = " discard"
------------------------------------------------------------------------------------
Key: JGRP-1079
URL:
https://jira.jboss.org/jira/browse/JGRP-1079
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.8
When we multicast OOB messages, and (1) the OOB pool has only 1 or 2 max threads, (2) no
queue and (3) a rejection_policy of "discard", then we can lose messages. The
messages are delivered (and retransmitted, if needed) correctly by NAKACK, but on the
receiver side, the extraction policy is incorrect.
The unit test is OOBTest.testOOBMessageLoss().
--
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