[jboss-jira] [JBoss JIRA] Commented: (JGRP-1010) TCPGOSSIP / TUNNEL: handle reconnecting on disconnect

[Bela Ban (JIRA)]

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

Bela Ban commented on JGRP-1010:
--------------------------------

If we have 2 GossipRouters A and B configured, and only B is disconnected, we need to make sure A does *not* reconnect again, or that if it does, a duplicate CONNECT message is discarded at the GR.

> TCPGOSSIP / TUNNEL: handle reconnecting on disconnect
> -----------------------------------------------------
>
>                 Key: JGRP-1010
>                 URL: https://jira.jboss.org/jira/browse/JGRP-1010
>             Project: JGroups
>          Issue Type: Task
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 2.8
>
>
> When a GossipRouter is not running, a RouterStub emits a callback that it failed to connect. The callback should schedule a recurring connect() task, until it succeeds. This should be done in both TUNNEL (done in 2.6.x, but not currently working in 2.8, due to the GR changes) and TCPGOSSIP (not even implemented in 2.6.x !).
> The reconnect logic needs to work with shared transports as well.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira