You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Babak Vahdat (Commented) (JIRA)" <ji...@apache.org> on 2011/11/11 14:56:51 UTC
[jira] [Commented] (CAMEL-4668) JpaConsumer - Should rollback if
processing of an exchange failed
[ https://issues.apache.org/jira/browse/CAMEL-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148497#comment-13148497 ]
Babak Vahdat commented on CAMEL-4668:
-------------------------------------
There's something baffling me here, which I like to understand/learn how it's possible that it works!
Looking at [1] there's no try/catch or onException(....).handled(true) or the likes on the route, so sending the payload SendEmail("kaboom@beer.org") should blow up with a CamelExecutionException wrapping the thrown IllegalArgumentException("Forced") through the usage of the template on the client side (in this case the test method testTXRollback()) but it doesn't!!!
For sure I'm missing some pieces of this tricky puzzle...
[1] https://svn.apache.org/repos/asf/camel/trunk/components/camel-jpa/src/test/java/org/apache/camel/processor/jpa/JpaTXRollbackTest.java
> 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