[jboss-jira] [JBoss JIRA] (JGRP-2069) UNICAST3: bypass or remove when running over TCP

[Bela Ban (JIRA)]

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

Bela Ban updated JGRP-2069:
---------------------------
    Fix Version/s: 3.6.11
                       (was: 3.6.10)


> UNICAST3: bypass or remove when running over TCP
> ------------------------------------------------
>
>                 Key: JGRP-2069
>                 URL: https://issues.jboss.org/browse/JGRP-2069
>             Project: JGroups
>          Issue Type: Enhancement
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>            Priority: Minor
>             Fix For: 3.6.11, 4.0
>
>
> When running over TCP as transport, UNICAST3 is still required: while TCP/IP retransmits messages reliably and also provides sender-FIFO ordering, the receiver's thread pool might be exhausted and thus the message might get rejected.
> However, *if* the regular and OOB thread pools are disabled, we could actually bypass (or completely remove) UNICAST3. If messages get dropped by a protocol further up the stack, however, there will be no retransmission in this case.
> SOLUTION:
> * Document this behavior
> * Emit an INFO message (or automatically bypass UNICAST3) when run over a TCP transport and both OOB and regular pools are disabled



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)