[jboss-jira] [JBoss JIRA] (JGRP-1578) UNICAST: lost ACK leads to endless retransmissions

[Bela Ban (JIRA)]

     [ https://issues.jboss.org/browse/JGRP-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bela Ban resolved JGRP-1578.
----------------------------

    Resolution: Done


Fixed according to suggest solution. Unit test is UNICAST_DroppedAckTest
                
> UNICAST: lost ACK leads to endless retransmissions
> --------------------------------------------------
>
>                 Key: JGRP-1578
>                 URL: https://issues.jboss.org/browse/JGRP-1578
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 3.2.7, 3.3
>
>
> - B sends a unicast message M to A
> - A drops the ACK(M) to B
> - B sends no further messages to A
> --> B will keep retransmitting M to A until it gets an ACK from A, or A leaves the cluster
> --> However, A will not send an ACK(M) to B, as the logic for acking only sends an ack if we did receive a message from B and it was successfully added to the retransmit table
> --> However, the retransmitted M will not get added to A's table, as M has already been received
> SOLUTION:
> - Always ack a message frpm B with the highest delivered seqno for B's table

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira