[
https://issues.apache.org/jira/browse/CAMEL-16039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482930#comment-17482930
]
Brad Harvey commented on CAMEL-16039:
-------------------------------------
Just adding a note to say my organisation no longer requires this - we ended up
implementing a basic polling consumer to consume JMS messages in batches.
> Reinstate Batch JMS Processing
> ------------------------------
>
> Key: CAMEL-16039
> URL: https://issues.apache.org/jira/browse/CAMEL-16039
> Project: Camel
> Issue Type: New Feature
> Components: camel-sjms
> Affects Versions: 3.8.0
> Reporter: Brad Harvey
> Priority: Major
> Fix For: 3.16.0
>
>
> Please provide a means of receiving multiple JMS messages as a batch in a
> single transaction.
> Our use case is to exchange JMS messages in order, quickly, with at least
> once delivery guarantee, but over a link with 10 to 15 ms latency.
> Processing multiple JMS messages in a single transaction is the way to meet
> this requirement as it greatly reduces the chatter over the wire:
> * For sending, we use the normal JMS component with a loop (using <split/>)
> inside the transaction.
> * For receiving (in 3.4.5) we use sjms-batch with an aggregation strategy.
> Example
> ** from
> sjms-batch:myqueue?aggregationStrategy=#groupedBodyAggregationStrategy&completionSize=300&asyncStartListener=true&keepAliveDelay=5000
> The sjms-batch component was removed as part of the overhaul of sjms, but
> there appears to be no alternative to the functionality it provided.
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
