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
{{ message }}
This repository was archived by the owner on Nov 10, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+11-4Lines changed: 11 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -356,10 +356,17 @@ An XML variant may look like:
356
356
````
357
357
358
358
The `SqsMessageDrivenChannelAdapter` exposes all `SimpleMessageListenerContainer` attributes to configure and one an
359
-
important of them is `deleteMessageOnException`, which is `true` by default. Having that to `false`, it is a
360
-
responsibility of end-application to delete message or not on exceptions. E.g. in the error flow on the
361
-
`error-channel` of this channel adapter. For this purpose a `AwsHeaders.RECEIPT_HANDLE` message header must be used
362
-
for the message deletion:
359
+
important of them is `messageDeletionPolicy`, which is set to `NO_REDRIVE` by default.
360
+
361
+
Possible values are:
362
+
363
+
-`ALWAYS` - Always deletes message automatically.
364
+
-`NEVER` - Never deletes message automatically.
365
+
-`NO_REDRIVE` - Deletes message if no redrive policy is defined.
366
+
-`ON_SUCCESS` - Deletes message when successfully executed by the listener method (no exception is thrown).
367
+
368
+
369
+
Having that to `NEVER`, it is a responsibility of end-application to delete message. For this purpose a `AwsHeaders.RECEIPT_HANDLE` message header must be used for the message deletion:
0 commit comments