[jira] [Commented] (CAMEL-6054) camel-hazelcast - Manage transactions with SEDA Consumer and improve the mapstore lifecycle

["Claus Ibsen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13575150#comment-13575150 ] 

Claus Ibsen commented on CAMEL-6054:
------------------------------------

Thomas, do you have an unit test to go with the patch?

Also i wonder if there is other hazelcast types that SEDA that can benefit from TX support.
Maybe also people should be allowed to configure transaction on|off.
                
> camel-hazelcast - Manage transactions with SEDA Consumer and improve the mapstore lifecycle
> -------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-6054
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6054
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-hazelcast
>    Affects Versions: 2.10.3
>         Environment: All camel applications with hazelcast component like seda consumer
>            Reporter: Thomas Vautrin
>              Labels: patch
>             Fix For: Future
>
>         Attachments: camel-hazelcast.patch
>
>
> The transactions are not started when the seda consumer is used.
> If the messages are stored in MapStore, seda consumer doesn't wait the end of transaction to remove data. It's a problem if the server crashes because data are lost.
> The patch allows to resolve this problem because the message in mapstore will be removed only when the transaction will be finished.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira