lhotari opened a new pull request, #24986: URL: https://github.com/apache/pulsar/pull/24986
### Motivation Received this log entry which caused unnecessary retries and latency on a Pulsar client: ``` failed to get Partitioned metadata : SSLEngine closed already org.apache.pulsar.shade.io.netty.handler.ssl.SslClosedEngineException: SSLEngine closed already ``` There's a similar issue that was resolved in reactor-netty with this PR https://github.com/reactor/reactor-netty/pull/2518 More details: * https://datatracker.ietf.org/doc/html/rfc8446#section-6.1 * [SSL / TLS: Is a server always required to respond to a close notify?](https://security.stackexchange.com/questions/82028/ssl-tls-is-a-server-always-required-to-respond-to-a-close-notify) * Since TLS 1.3, it's not even part of the spec to have a response. In TLS 1.2, it's optional. ### Modifications - Close the channel immediately when TLS close_notify event is received ### Documentation <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. --> - [ ] `doc` <!-- Your PR contains doc changes. --> - [ ] `doc-required` <!-- Your PR changes impact docs and you will update later --> - [x] `doc-not-needed` <!-- Your PR changes do not impact docs --> - [ ] `doc-complete` <!-- Docs have been already added --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
