[
https://issues.apache.org/jira/browse/CASSANDRA-16277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243530#comment-17243530
]
Jon Meredith commented on CASSANDRA-16277:
------------------------------------------
[~aleksey] should the
cefe43b06bb1c0dd3bd362638cc56e0fc1f78ddb have also updated the Netty Version
numbers in build.xml?
> 'SSLEngine closed already' exception on failed outbound connection
> ------------------------------------------------------------------
>
> Key: CASSANDRA-16277
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16277
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Internode
> Reporter: Aleksey Yeschenko
> Assignee: Aleksey Yeschenko
> Priority: Normal
> Fix For: 4.0-beta4
>
>
> Occasionally Netty will invoke
> {{OutboundConnectionInitiator#exceptionCaught()}} handler to process an
> exception of the following kind:
> {code}
> io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed:
> Connection reset by peer
> {code}
> When we invoke {{ctx.close()}} later in that method, the listener, set up in
> {{channelActive()}}, might be
> failed with an {{SSLException("SSLEngine closed already”)}} by Netty, and
> {{exceptionCaught()}} will be invoked
> once again, this time to handle the {{SSLException}} triggered by
> {{ctx.close()}}.
> The exception at this stage is benign, and we shouldn't be double-logging the
> failure to connect.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
