[jboss-jira] [JBoss JIRA] (JGRP-1428) UnicastRequest and GroupRequest should mark a target as suspected if the target has already left the cluster at creation time

[ https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-1428: ----------------------------------------------- JBoss JIRA Server <jira-update(a)redhat.com&gt; made a comment on [bug 801734|https://bugzilla.redhat.com/show_bug.cgi?id=801734] Bela Ban <bela(a)jboss.com&gt; made a comment on jira JGRP-1428 Here's a scenario which could still reproduce the bug: - The current view is is V1 - RequestCorrelator.receiveView() installs a new view V2 and starts iterating over requests - A new Request is added to 'requests'. Because the iterator above iterates on a ConcurrentHashmap, it will iterate over a copy and *not* call viewChange(V2) on the request ! - RequestCorrelator.send(Unicast)Request() now calls viewChange(V1) on the request. V1 is used because the assignment of V2 to RequestCorrelator.view has *not* yet happened ! - RequestCorrelator.receiveView() now assigns V2 to this.view --> In this scenario, we do *not* call viewChange(V2) on the request, but only use the old view V1 ! ==> Moving the assignment of V2 to this.view *before* the iteration should fix the issue -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira