[JBoss JIRA] Created: (JGRP-1079) OOB messages are discarded when pool size is small and rejection_policy = " discard"
4:44 a.m.
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
4:52 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-1079) OOB messages are discarded when pool size is small and rejection_policy = " discard"
[
https://jira.jboss.org/jira/browse/JGRP-1079?page=com.atlassian.jira.plug...
]
Bela Ban commented on JGRP-1079:
--------------------------------
Same with UNICAST
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
5:48 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-1079) OOB messages are discarded when pool size is small and rejection_policy = " discard"
[
https://jira.jboss.org/jira/browse/JGRP-1079?page=com.atlassian.jira.plug...
]
Bela Ban commented on JGRP-1079:
--------------------------------
A workaround is to configure the OOB thread pool with a rejection policy of
"run", or to make it big enough to handle all OOB messages (not feasible)
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
9:31 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-1079) OOB messages are discarded when pool size is small and rejection_policy = " discard"
[
https://jira.jboss.org/jira/browse/JGRP-1079?page=com.atlassian.jira.plug...
]
Bela Ban commented on JGRP-1079:
--------------------------------
SOLUTION: whenever an OOB message is passed up the stack, we set a transient flag
OOB_DELIVERED in the message (atomically, if not set !) and pass the message up if we were
able to set the flag, else discard it.
After that, we try to remove as many OOB messages from the NakReceiverWindow and pass
those messages up as well if the OOB_DELIVERED flag is not set.
Transient flags in a message are never marshalled or copied to a new message.
This change allowed us to remove the oob_loopback hashset
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
4:52 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-1079) OOB messages are discarded when pool size is small and rejection_policy = " discard"
[
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
6:14 a.m.
New subject: [JBoss JIRA] Resolved: (JGRP-1079) OOB messages are discarded when pool size is small and rejection_policy = " discard"
[
https://jira.jboss.org/jira/browse/JGRP-1079?page=com.atlassian.jira.plug...
]
Bela Ban resolved JGRP-1079.
----------------------------
Resolution: Done
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
6100
days inactive
6122
days old
5 comments
1 participants
participants (1)
-
Bela Ban (JIRA)