You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Scott England-Sullivan (JIRA)" <ji...@apache.org> on 2013/10/16 21:01:43 UTC

[jira] [Assigned] (CAMEL-6863) Batch SJMS consumer - Commit issues

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

Scott England-Sullivan reassigned CAMEL-6863:
---------------------------------------------

    Assignee: Scott England-Sullivan

> Batch SJMS consumer - Commit issues
> -----------------------------------
>
>                 Key: CAMEL-6863
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6863
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-sjms
>    Affects Versions: 2.11.0, 2.11.1, 2.11.2, 2.12.0, 2.12.1
>            Reporter: Florent Vansiliette
>            Assignee: Scott England-Sullivan
>
> SJMS Consumer does not support a route with the Aggregation Pattern. 
> When an exchange comes into an aggregate, a copy of this exchange is done and the original exchange continues its processing. When the processing of the original exchange is finished, its completion will be executed.
> So with the SJMS component, the completion of the last exchange of the batch might occurs before the aggregated message finishes its processing. So even if the aggregated exchange fails, the JMS session is already committed and messages are lost.
> Another issue is with the timeout which triggers a commit no matter an exchange is still inflight or not.
>  
> In general, the commit of the transaction triggered by the timeout should know if an exchange is still inflight and only commit (or rollback in case the exchange is failed) the transaction when the exchange is completed.
> More info here:
> http://camel.465427.n5.nabble.com/SJMS-implementation-Batch-Consumer-td5741291.html



--
This message was sent by Atlassian JIRA
(v6.1#6144)