[
https://issues.apache.org/jira/browse/THRIFT-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16886531#comment-16886531
]
Rocco Corsi commented on THRIFT-4885:
-------------------------------------
Are you saying it is a duplicate of THRIFT-4888? Or some other issue?
Forgetting to ignore SIGPIPE?
Just to be clear this issue happens very rarely for us in our in production
application. We are ignoring SIGPIPE, so is not that.
It appears to be a race condition when client disconnects at same time as
server is attempting to send a message to client. Might require heavy
traffic. You might never see this unless you have the right combination of
factors.
In the process of writing a test tool application that will reproduce the issue
and then hopefully the issue will be easier to investigate. Will attach
valgrind output and core dump from that when available.
> TSSLSocket crash during write
> ------------------------------
>
> Key: THRIFT-4885
> URL: https://issues.apache.org/jira/browse/THRIFT-4885
> Project: Thrift
> Issue Type: Bug
> Components: C++ - Library
> Affects Versions: 0.10.0
> Reporter: op
> Priority: Major
> Attachments: patch.txt
>
>
> It happens that a race condition between TSSLSocket::write and
> TSSLSocket::close causes the application to crash. This issue has also been
> detected by Valgrind.
>
> This is the core dump backtrace
> #1 0x00007f08549b2291 in BIO_write () from /lib64/libcrypto.so.1.0.0
> #2 0x00007f084fdbbb62 in ?? () from /lib64/libssl.so.1.0.0
> #3 0x00007f084fdbc256 in ?? () from /lib64/libssl.so.1.0.0
> #4 0x00007f085466657c in apache::thrift::transport::TSSLSocket::(write
> (this=0x7f07a0001060, buf=0x7f07a4b6d1ac "", len=4) at
> src/thrift/transport/TSSLSocket.cpp:387
>
> See the patch in attachment.
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
