camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott England-Sullivan (JIRA)" <>
Subject [jira] [Updated] (CAMEL-6863) Batch SJMS consumer - Commit issues
Date Wed, 16 Oct 2013 19:03:42 GMT


Scott England-Sullivan updated CAMEL-6863:

    Affects Version/s:     (was: 2.12.1)
                           (was: 2.11.2)
                           (was: 2.12.0)
                           (was: 2.11.1)
                           (was: 2.11.0)

> Batch SJMS consumer - Commit issues
> -----------------------------------
>                 Key: CAMEL-6863
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-sjms
>    Affects Versions: 2.13.0
>            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:

This message was sent by Atlassian JIRA

View raw message