[jboss-jira] [JBoss JIRA] Commented: (JGRP-717) Message ordering protocol for TCP unicasts

[Bela Ban (JIRA)]

    [ http://jira.jboss.com/jira/browse/JGRP-717?page=comments#action_12417509 ] 
            
Bela Ban commented on JGRP-717:
-------------------------------

[Bela]
Aha, the reason for the exception on send() is we DON'T remove the connection at B when A closes its side !  In BasicConnectionTable:684 you can see that remove() is commented. The reason for this was that members could get into a state where the mutually close their connections to each other, and so I thought it was better to let them close the connections just-in-time when data was sent.

But you're right: one tiny little exception sending data and we end up with a lost sequence number, and thus a stuck receiver. I'll remove xmit_off


> Message ordering protocol for TCP unicasts
> ------------------------------------------
>
>                 Key: JGRP-717
>                 URL: http://jira.jboss.com/jira/browse/JGRP-717
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Brian Stansberry
>         Assigned To: Bela Ban
>             Fix For: 2.7, 2.6.3
>
>
> With the introduction of a thread pool in the TCP protocol, the ability to relying on TCP/IP to guarantee ordering of unicast messages is lost. See JGRP-716.  Solution is to add UNICAST to TCP-based stacks that use a thread pool.  This is not ideal since UNICAST adds overhead for reliable transmission (sending ACKs, retaining sent messages for retransmission) and this overhead is unnecessary with TCP.  Request is for a protocol with the message ordering functionality of UNICAST but without the reliable transmission features.

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