-
Notifications
You must be signed in to change notification settings - Fork 858
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SNS/SQS SdkClientException Server failed to send complete response #1520
Comments
Hi @alejandrod can you try reducing connectionMaxIdleTimeout or upgrading to the latest sdk? In https://github.com/aws/aws-sdk-java-v2/blob/master/CHANGELOG.md#21019-2019-11-18 |
Hi, hopefully the advice to change the connectionMaxIdleTimeout worked for you. Please feel free to re-open if you are still seeing this problem with the new setting. |
Looks like it works ! Thanks! version 2.10.30 |
The issue is still happening in versions 2.10.19 and latest version 2.13.34. Context: Also, we are using localstack (https://github.com/localstack/localstack), a local AWS cloud stack for unit testing. Let me know if any information is required, happy to provide. Code that uploads files to S3:
S3AsyncClient builder:
The SDKException stacktrace is pretty much same in both versions, except exception message. 2.10.19 stacktrace:
2.13.34 stacktrace:
|
…8fa011d40 Pull request: release <- staging/84586be3-e69a-4e40-ab2c-1d98fa011d40
HI, have read this post and others like it and I notice that you never could check if the updates on aws-sdk-java-v2 worked to fix your bug. I am currently using version 2.10.41 and the error persists in this version. Did you find out how to fix this bug ? |
This issue has been reported before for S3 and rapid uploads as described here:
#1122
#452
This is for SNS/SQS
Expected Behavior
No error should be thrown or a retry should be performed
Current Behavior
We randomly get this exception:
Possible Solution
Steps to Reproduce (for bugs)
Your Environment
2.10.18
but I've been having issues for a long time now. Since 2.5.x I thinkThe text was updated successfully, but these errors were encountered: