-
Notifications
You must be signed in to change notification settings - Fork 859
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
SqsAsyncClient is failing unpredictably during streaming #1466
Comments
Thank you for the detailed report. I will try to reproduce it. |
I was not able to reproduce When you said it stopped receiving messages from the queue, did you mean all requests failed of I will continue investigating. |
#1476 has been merged to address the issue with unresusable connections getting reused and the change will be included in the next release. |
Hi @jaylynstoesz, a fix has been released as part of |
Hi @jaylynstoesz are you still seeing the issue? |
Closing the issue due to no response. Feel free to reopen if you continue to see the issue with the latest version. |
I'm reading from SQS via Alpakka using the async client. It appears to randomly stop receiving messages from the queue, anywhere from a few minutes to a few hours apart. It appears to happen more frequently when volume is higher, though not necessarily during peak times.
Expected Behavior
My service continuously polls messages from SQS, processes them, and deletes them from the queue. Invalid messages are sent to a dead letter queue. In the attached screenshot of the queue monitoring dashboard, I would expect the NumberOfMessagesReceived graph to match the NumberOfMessagesSent graph.
Current Behavior
The SQS client randomly throws
java.io.IOException: Server failed to send complete response
and stops polling messages.Steps to Reproduce (for bugs)
Error stack trace:
Context
This service is designed to stream business-critical accounting events in order to respond to charges against customer accounts in real time. So, if the service stops polling SQS messages, this prevents us from responding as events occur and could incur significant costs to the business.
Your Environment
Kotlin: 1.3.41
Netty & SQS Java SDK: 2.9.15
CC: @debora-ito re: #1122 (comment)
The text was updated successfully, but these errors were encountered: