zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Han (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-1684) Failure to update socket addresses on immedate connection
Date Mon, 13 Mar 2017 16:22:00 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Han updated ZOOKEEPER-1684:
-----------------------------------
    Fix Version/s:     (was: 3.5.3)
                   3.5.4

> Failure to update socket addresses on immedate connection
> ---------------------------------------------------------
>
>                 Key: ZOOKEEPER-1684
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1684
>             Project: ZooKeeper
>          Issue Type: Bug
>            Reporter: Shevek
>             Fix For: 3.5.4, 3.6.0
>
>         Attachments: ZOOKEEPER-1684.diff
>
>
> I quote:
> void registerAndConnect(SocketChannel sock, InetSocketAddress addr)
> throws IOException {
> sockKey = sock.register(selector, SelectionKey.OP_CONNECT);
> boolean immediateConnect = sock.connect(addr);
> if (immediateConnect)
> { sendThread.primeConnection(); }
> }
> In the immediate case, there are several bugs:
> a) updateSocketAddresses() is never called, as it is when the select-loop in doTransport().
This means that clientCnxnSocket.getRemoteSocketAddress() will return null for the lifetime
of this socket?
> b) CONNECT still in the interest set for the socket.
> c) updateLastSendAndHeard() is never called either.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message