[
https://issues.apache.org/jira/browse/CAMEL-18350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Espen Andreassen updated CAMEL-18350:
-------------------------------------
Description:
*Summary:*
When configuring the camel consumer with props "breakOnFirstError" = "true",
the application will reconsume all messages on topic on error depending on poll
size. Camel should only have reconsumed the failed message/message batch is
such cases.
I've created a project on github with a failing test that recreates the issue:
[https://github.com/espeandr/camel-kafka-incorrectly-reconsumes-entire-topic-demo]
was:
*Summary:*
When configuring the camel consumer with props "breakOnFirstError" = "true" and
"maxPollRecords" = "1", camel reconsumes all messages on topic on error. Camel
should only have reconsumed the failed message is such cases.
I configure the component like this to approximate an "exactly once" delivery
policy (in comibnation with manual commits).
I've created a project on github with a failing test that recreates the issue:
[https://github.com/espeandr/camel-kafka-incorrectly-reconsumes-entire-topic-demo]
> camel-kafka: combination of breakOnFirstError and maxPollRecords causes camel
> to reconsume all records on error
> ----------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-18350
> URL: https://issues.apache.org/jira/browse/CAMEL-18350
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka
> Affects Versions: 3.18.0
> Reporter: Espen Andreassen
> Priority: Minor
> Fix For: 3.20.0
>
>
> *Summary:*
> When configuring the camel consumer with props "breakOnFirstError" = "true",
> the application will reconsume all messages on topic on error depending on
> poll size. Camel should only have reconsumed the failed message/message batch
> is such cases.
> I've created a project on github with a failing test that recreates the
> issue:
> [https://github.com/espeandr/camel-kafka-incorrectly-reconsumes-entire-topic-demo]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
