[
https://issues.apache.org/jira/browse/CAMEL-17443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17469951#comment-17469951
]
Yasser Zamani commented on CAMEL-17443:
---------------------------------------
Thanks but
{code:java}
onException(RollbackExchangeException.class).log("YASSER").logExhausted(false);
{code}
didn't help neither global nor on route. I see one WARN from
{{DefaultErrorHandler}}, then I see "YASSER", then I see another WARN from
again {{DefaultErrorHandler}} (but a multiline log this time), then I see one
from {{TransactionErrorHandler}} of Camel JTA, then one from
{{GenericFileOnCompletion}} of Camel file component.
No problem. Currently we can live with them. But *it would be awesome if file
component was able to not move the file and abort exchange when there's
.markRollbackOnly() specified. Similar behavior like now that I've used
.rollback() but with no exception. that's all what this ticket is about.*
> .markRollbackOnly() doesn't abort exchange
> ------------------------------------------
>
> Key: CAMEL-17443
> URL: https://issues.apache.org/jira/browse/CAMEL-17443
> Project: Camel
> Issue Type: Wish
> Affects Versions: 3.14.0
> Reporter: Yasser Zamani
> Priority: Major
>
> {code:java}
> from("file:./target/source?move=../archive")
> .transacted()
> .choice().when(minAgePredicate).markRollbackOnly()
> .otherwise()
> ....
> {code}
> moves the consumed file to the archive folder even when it's marked to
> rollback!
> When I replace {{.markRollbackOnly()}} with {{.rollback()}}, it works as
> expected i.e. it doesn't move the file to the archive folder and polls it
> again and again until {{minAgePredicate}} satisfied. But the problem is that
> it logs a lot of warnings i.e. in each poll it warns about the rollback.
> As per docs, I wished I could ask Camel to just rollback and abort/stop
> exchange *silently* with *.markRollbackOnly()*.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
