[
https://issues.apache.org/jira/browse/CAMEL-17443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471174#comment-17471174
]
Claus Ibsen commented on CAMEL-17443:
-------------------------------------
Using rollbackOnly without transactions is "interresting" thought. It would
mean we could regard the uow as failed if exception != null or rollbackonly =
true. However most consumers would expect that it failed due to an exception,
so we may have to set an exception at this stage (so there is an exception) but
the error handler would not log anything as there was nothing before.
> .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)
