[
https://issues.apache.org/jira/browse/CAMEL-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149027#comment-13149027
]
Claus Ibsen commented on CAMEL-4668:
------------------------------------
Sending to JPA does *not* fail. So the 3 template code lines works fine.
Its the Camel route that fails. The JPA consumer is scheduled, so it will poll
again later (after 2sec). And it will keep failing due that hardcoded exception
being thrown. But foo and bar records will be fine, but as they are part of the
same TX, they will also rollback. So the foo and bar counter will keep
incrementing.
> JpaConsumer - Should rollback if processing of an exchange failed
> -----------------------------------------------------------------
>
> Key: CAMEL-4668
> URL: https://issues.apache.org/jira/browse/CAMEL-4668
> Project: Camel
> Issue Type: Bug
> Components: camel-jpa
> Affects Versions: 2.7.4, 2.8.2
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.7.5, 2.8.3, 2.9.0
>
>
> If a JPA consumer pickup X messages and then one of those messages fails to
> be processed and throws an exception, then the JPA consumer should detect
> this and mark the TX as rollback.
> Currently there is a flaw which causes the JPA consumer to commit the batch.
> See nabble
> http://camel.465427.n5.nabble.com/Misleading-jmx-statistics-on-jpa-component-tp4960503p4960503.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
