[jboss-jira] [JBoss JIRA] (JGRP-1664) UNICAST3: ack on reception versus ack on delivery

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791170#comment-12791170 ] 

Bela Ban commented on JGRP-1664:
--------------------------------

The issue with a single message was that it was acked only after the application callback returned; therefore an ack would not be sent until the callback ended. This would cause unneeded retransmissions of the message by the sender, until the ack was received.
                
> UNICAST3: ack on reception versus ack on delivery
> -------------------------------------------------
>
>                 Key: JGRP-1664
>                 URL: https://issues.jboss.org/browse/JGRP-1664
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 3.4
>
>
> In UNICAST3, if ack_batches_immediately is true, a message batch is acked *before* delivering it. So this is basically acking on *reception* rather than *delivery*.
> However, this is not done for single messages. I could change the ack_batches_immediately to ack_on_reception, and  - if true - ack single messages also before they're delivered.
> Thus we'd have a single property which governs whether single messages or message batches are acked on reception or delivery.

--
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