[
https://issues.apache.org/jira/browse/CAMEL-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149180#comment-13149180
]
Babak Vahdat commented on CAMEL-4668:
-------------------------------------
@Claus,
As Preben tries to push his JMX expectations I insist on my Routing
expectations. Really not an easy job for you, but I really appreciate your
contribution.
You said:
2: Then the route is started, which starts the consumer, it then pickup the 3
messages. And fail processing the last message. Which forces all 3 to rollback.
So when it poll again, it find the 3 messages, and try again etc.
However a slight modification of this test case by me (see the attachment)
proves the opposite, that is, after routing is completed there're *3* rows in
the table! I've a suspection that somewhere along the way the thrown
IllegalArgumentException("Forced") is simply swallowed!
Again my expectation is that the call to
{code}
template.sendBody("jpa://" + SendEmail.class.getName(), new
SendEmail("kab...@beer.org"));
{code}
Should blow up with a CamelExecutionException, but that's another story which I
still don't understand :-(
> 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
>
> Attachments: JpaTXRollbackTest.patch
>
>
> 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
