Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

SQS failures are not immediately reported back to AWS? #1312

Closed
achuinard opened this issue Dec 30, 2024 · 0 comments
Closed

SQS failures are not immediately reported back to AWS? #1312

achuinard opened this issue Dec 30, 2024 · 0 comments

Comments

@achuinard
Copy link

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.

@awspring awspring locked and limited conversation to collaborators Jan 1, 2025
@tomazfernandes tomazfernandes converted this issue into discussion #1313 Jan 1, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant