You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Thomas Vautrin (JIRA)" <ji...@apache.org> on 2013/02/11 10:25:14 UTC
[jira] [Comment Edited] (CAMEL-6054) camel-hazelcast - Manage
transactions with SEDA Consumer and improve the mapstore lifecycle
[ https://issues.apache.org/jira/browse/CAMEL-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13575695#comment-13575695 ]
Thomas Vautrin edited comment on CAMEL-6054 at 2/11/13 9:24 AM:
----------------------------------------------------------------
Claus,
I updated the patch with the "transactionnal" attribut to enable or not the transaction. (Disable by default)
was (Author: tvautrin):
Hazelcast patch with transaction and the configuration
> 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: 2.11.0
>
> 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