You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/15 16:01:55 UTC

[jira] [Resolved] (CAMEL-4683) JpaConsumer - Add option to control if consumer should run in transacted mode and rollback all if one exchange failed

     [ https://issues.apache.org/jira/browse/CAMEL-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-4683.
--------------------------------

    Resolution: Fixed
    
> JpaConsumer - Add option to control if consumer should run in transacted mode and rollback all if one exchange failed
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-4683
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4683
>             Project: Camel
>          Issue Type: Improvement
>          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
>
>
> See nabble
> http://camel.465427.n5.nabble.com/Misleading-jmx-statistics-on-jpa-component-tp4960503p4960503.html
> We should add option {{consumer.transacted}} to allow end users to control if they want the JpaConsumer to run in transacted mode, where by if one exchange failed to be processed, the entire batch is rolled back. If not, then all the good messages will be committed, and only the failed message will rollback.

--
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