You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, my understanding is that my JMS listener used to immediately report a processing failure back to SQS, which would cause SQS to re-fire / redrive the message and try again. However, this new SQS consumer seems to not report failures at all back to AWS, instead just relying on AWS to refire the message based on the SQS visibility timeout.
Doesn't it make more sense for my app to immediately report failures and retry? Is this something configurable with the new Spring Cloud starter? Or maybe I'm not understanding something 100% right.
The text was updated successfully, but these errors were encountered:
I am moving an older SQS consumer app that used to use JMS with https://github.com/awslabs/amazon-sqs-java-messaging-lib to now use the new Spring Cloud AWS Starter with @SqsListener annotations.
However, my understanding is that my JMS listener used to immediately report a processing failure back to SQS, which would cause SQS to re-fire / redrive the message and try again. However, this new SQS consumer seems to not report failures at all back to AWS, instead just relying on AWS to refire the message based on the SQS visibility timeout.
Doesn't it make more sense for my app to immediately report failures and retry? Is this something configurable with the new Spring Cloud starter? Or maybe I'm not understanding something 100% right.
The text was updated successfully, but these errors were encountered: