[jira] [Updated] (CAMEL-9405) Amazon SQS message deletion behaviour change on exception

["Stephen Souness (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-9405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephen Souness updated CAMEL-9405:
-----------------------------------
    Attachment: SqsConsumerSedaTest.java

Unit test demonstrating that deletion occurs.

> Amazon SQS message deletion behaviour change on exception
> ---------------------------------------------------------
>
>                 Key: CAMEL-9405
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9405
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-aws
>    Affects Versions: 2.14.3
>            Reporter: Stephen Souness
>         Attachments: SqsConsumerSedaTest.java
>
>
> After upgrading applications from Camel 2.15.2 to Camel 2.15.3 we noticed a change in behaviour around the handling of a message from an SQS queue when a processing stage throws an exception.
> Previously the message would not be deleted, and would become available to the SQS again.
> After the upgrade, messages are deleted even if an exception occurs during the processing stage.
> I will attach a unit test which demonstrates the behaviour by:
>  - including a mock process which throws an exception
>  - asserting that there is no call to delete a message.
> I believe that the commit which changed the behaviour is:
> https://github.com/apache/camel/commit/bd10c49bdcdbe6181e35461c449ea61db9a13bf1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)