[jboss-jira] [JBoss JIRA] (JGRP-1586) UNICAST / UNICAST2: connection reaping should flush pending messages

[Alan Field (JIRA)]

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

Alan Field commented on JGRP-1586:
----------------------------------

I think the property name is 'conn_expiry_timeout', instead of 'conn_expiry_time'
                
> UNICAST / UNICAST2: connection reaping should flush pending messages
> --------------------------------------------------------------------
>
>                 Key: JGRP-1586
>                 URL: https://issues.jboss.org/browse/JGRP-1586
>             Project: JGroups
>          Issue Type: Task
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 3.3
>
>
> In UNICAST/UNICAST2, a connection reaper closes idle connections after conn_expiry_time ms. The closing of a connection from A to B simply destroys and removes the entry for B (on A).
> However, if there are pending (unacked) messages in B's connection entry, they will be dropped.
> SOLUTION: 
> Instead of simply destroying the connection entry for B, we should mark the entry as 'closing', so no more messages are added, and flush any pending messages. Perhaps send a CLOSE message to B.
> WORKAROUND:
> Set UNICAST(2).conn_expiry_time=0. This doesn't run the connection reaper

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