[jira] [Commented] (CASSANDRA-16277) 'SSLEngine closed already' exception on failed outbound connection

["Alex Petrov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-16277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17233704#comment-17233704 ] 

Alex Petrov commented on CASSANDRA-16277:
-----------------------------------------

LGTM, +1.

> '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
>
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org