1 Answer
- Newest
- Most votes
- Most comments
0
I have had this question also posted on the Github for the C++ SDK, Sergey has provided a solution:
Could you please check if setting Aws::SDKOptions.httpOptions.installSigPipeHandler option will fix your issue?
Aws::SDKOptions options; options.httpOptions.installSigPipeHandler = true;
Also, from https://docs.aws.amazon.com/sdk-for-cpp/v1/developer-guide/basic-use.html#sdk-setting-options:
When installSigPipeHandler is true, the SDK for C++ uses a handler that ignores SIGPIPE signals. For more information on SIGPIPE, see Operation Error
Signals on the GNU Operating System website. For more information on the curl handler, see CURLOPT_NOSIGNAL explained on the curl website.
The underlying libraries of curl and OpenSSL can send a SIGPIPE signal to notify when the remote side closes a connection. These signals must be handled > by the application. For more information this curl functionality, see libcurl thread safety on the curl website. This behavior is not automatically built-in to the SDK because signal handlers are global for each application and the library is a
dependency for the SDK.
Best regards, Sergey
And the github discussion in it is: https://github.com/aws/aws-sdk-cpp/discussions/2494
answered a year ago
Relevant content
- asked 2 years ago
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 10 months ago