[CASSANDRA-16277] 'SSLEngine closed already' exception on failed outbound connection

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-beta4, 4.0
• Component/s: Messaging/Internode
• Bug Category: Degradation - Other Exception
• Severity: Low
• Complexity: Normal
• Discovered By: User Report
• Platform: All
• Since Version: 4.0-alpha1

Source Control Link

e572c8fca0c5cd68229b8db8d4915817d5d49daf

Test and Documentation Plan

Run existing tests

• Assignee: Aleksey Yeschenko
• Reporter: Aleksey Yeschenko

Authors

Aleksey Yeschenko

Reviewers

Aleksey Yeschenko, Alex Petrov, Norman Maurer

• Created: 16/Nov/20 17:09
• Updated: 03/Jan/21 16:58
• Resolved: 18/Nov/20 14:18

Description

Occasionally Netty will invoke OutboundConnectionInitiator#exceptionCaught() handler to process an exception of the following kind:

io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer

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.