Skip to content
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

Add BackOff when SQS Poll throws an exception #1008

Merged
merged 1 commit into from
Feb 2, 2024

Conversation

tomazfernandes
Copy link
Contributor

Fixes #714

Adds support for a Spring Retry BackOffPolicy to be executed when an exception is thrown by a polling thread.

Adds the configuration to ContainerOptions with a exponential default of 1000ms / 2.0 / 10000ms.

@github-actions github-actions bot added component: sqs SQS integration related issue type: documentation Documentation or Samples related issue labels Jan 3, 2024
Fixes awspring#714

Adds support for a Spring Retry BackOffPolicy to be executed when an exception is thrown by a polling thread.

Adds the configuration to ContainerOptions with a exponential default of 1000ms / 2.0 / 10000ms.
@maciejwalkowiak maciejwalkowiak added this to the 3.2 milestone Jan 4, 2024
@tomazfernandes tomazfernandes merged commit 49d7ef4 into awspring:main Feb 2, 2024
4 checks passed
@tomazfernandes tomazfernandes deleted the GH-714 branch February 2, 2024 23:53
@maciejwalkowiak maciejwalkowiak modified the milestones: 3.2.0 RC1, 3.1.1 Mar 10, 2024
@CasaSky
Copy link

CasaSky commented Apr 6, 2024

@tomazfernandes @maciejwalkowiak how to integrate exponential retry | pollBackOffPolicy ? I found it in the interface ContainerOptionsBuilder but it seems not to be supported yet in version 3.1.1? Or is it just becoming a default behavior for SQS Listeners?
Is there an example how to use it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: sqs SQS integration related issue type: documentation Documentation or Samples related issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SQS back off time equivalent in 3.x.x
3 participants