[
https://issues.apache.org/jira/browse/IMPALA-13676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Csaba Ringhofer closed IMPALA-13676.
------------------------------------
Resolution: Duplicate
> Closing ssl server sockets can hang on OpenSSL 3.2
> --------------------------------------------------
>
> Key: IMPALA-13676
> URL: https://issues.apache.org/jira/browse/IMPALA-13676
> Project: IMPALA
> Issue Type: Bug
> Reporter: Csaba Ringhofer
> Priority: Critical
>
> example: https://jenkins.impala.io/job/rocky-9.2-from-scratch/18/
> The test code is hanging in the ssl client while the server code seems to
> hang while closing the socket:
> {code}
> 1
> thrift-server-test!apache::thrift::transport::TSSLSocket::waitForEvent(bool)
> [TSSLSocket.cpp : 881 + 0xa]
> 2
> thrift-server-test!apache::thrift::transport::TSSLSocket::initializeHandshake()
> [TSSLSocket.cpp : 683 + 0x12]
> 7 thrift-server-test!apache::thrift::transport::TBufferedTransport::close()
> [TBufferTransports.cpp : 133 + 0x3]
> 8
> thrift-server-test!apache::thrift::server::TAcceptQueueServer::Task::run()
> [TAcceptQueueServer.cpp : 111 + 0x3]
> {code}
> My impression is that TBufferedTransport / TSSLSocket don't interact well
> here as TBufferedTransport tries to flush the underlying transport even if
> there was never ever any successful communication, leading to trying to to
> ssl handshake during close. I don't how the openssl/OS update causes
> different behavior.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
