[jboss-jira] [JBoss JIRA] Commented: (JGRP-523) Multicasts fail after a merge
[ http://jira.jboss.com/jira/browse/JGRP-523?page=comments#action_12364533 ]
Bela Ban commented on JGRP-523:
-------------------------------
This can be reproduced with MergeTest.testTwoMerges().
The issue is that NAKACK.down(TMP_VIEW) (received just before a merge view) creates new
NakReceiverWindows for each sender S which is not in the xmit_table with seqno=0.
When we do receive the merge view, NAKACK.mergeDigests() does *not* set the lowest and
highest seqnos for S's NRW as it is already present in xmit_table ! So the highest
delivered seqno is 0, whereas the real seqno might be 100, so the next time we send a
message, retransmission for 1-100 kicks in !
Solution: comment adjustReceivers() in down(TMP_VIEW), so we don't actually create new
entries for new members with seqno=0, but wait until down(VIEW_CHANGE) is received (where
we *do* call adjustReceivers()).
Multicasts fail after a merge
-----------------------------
Key: JGRP-523
URL: http://jira.jboss.com/jira/browse/JGRP-523
Project: JGroups
Issue Type: Bug
Affects Versions: 2.5
Reporter: Bela Ban
Assigned To: Bela Ban
Priority: Critical
Fix For: 2.5
To reproduce:
- Start GossipRouter
- Start 2 Draws with tunnel.xml, connecting to the GR
- Paint a bit in the 2 windows, to generate messages (and thus change the digests)
- Kill GR
- When both Draw instances become cluster singletons, start GR again
==> Observe that we get messages that indicate a requested retransmission couldn't
be satisfied because the message was not found:
14:38:16,203 [WARN] [OOB Thread,demo,192.168.5.2:4397] NAKACK.handleMessage():
192.168.5.2:4397] discarded message from non-member 192.168.5.2:4393, my view is
[192.168.5.2:4397|2] [192.168.5.2:4397]
14:38:16,890 [WARN] [OOB Thread,demo,192.168.5.2:4393] NAKACK.handleMessage():
192.168.5.2:4393] discarded message from non-member 192.168.5.2:4397, my view is
[192.168.5.2:4393|2] [192.168.5.2:4393]
--
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