NAKACK/UNICAST: atomic boolean vars might lead to message not getting processed
immediately
-------------------------------------------------------------------------------------------
Key: JGRP-934
URL:
https://jira.jboss.org/jira/browse/JGRP-934
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Minor
Fix For: 2.9
When we have a thread T1 adding a message and T2 removing them, the following situation
might occur:
- T2 removes a null message
- T2 terminates remove loop
- T1 adds message M1 and tries to set the atomic var to true, result is false
- T2 sets the atomic boolean var from true to false
- T1 returns
- T2 returns
==> M1 is not getting processed until the next thread dlivers a message !
This is a very rare case, but still needs to be fixed, maybe with 2 overlapping atomic
vars ?
--
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