[THRIFT-5456] ServerSocket doesn't ignore SIGPIPE

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.16.0
• Component/s: C++ - Library
• Assignee: Kevin Wojniak
• Reporter: Kevin Wojniak
• Created: 16/Aug/21 21:02
• Updated: 15/Feb/22 21:41
• Resolved: 21/Oct/21 21:12

Description

TServerSocket sets up many socket options, but unlike TSocket, it doesn't disable SIGPIPE.

One example for how this can be triggered is the server receives a request, but takes too long to process it. The sender then times out, and potentially closes its sockets. The server then completes the request, and then attempts to write back the result. Since the socket is now closed, a SIGPIPE signal is sent to the process, and if that signal isn't ignored, the process would crash, with a potential -13 exit code.

Issue Links

• links to: GitHub Pull Request #2440