You could use BatchMessageListenerContainer [1] instead of DefaultMessageListenerContainer.
An option to provide a specific MessageListenerContainer is to used the 'consumerType' parameter from the JMS component and set it to 'Custom' and provide the option 'messageListenerContainerFactoryRef' [2]. [1] http://docs.spring.io/spring-batch/apidocs/org/springframework/batch/container/jms/BatchMessageListenerContainer.html [2] http://camel.apache.org/jms.html#JMS-Alltheotheroptions > On 18 Nov 2015, at 14:17, deepak_a <angesh...@gmail.com> wrote: > > Hi, > > As mentioned in my previous post - I am developing a bridge that will set > b/w ActiveMQ and TIBCO EMS. > > My aim is to use a XATransactionManager (like Atomikos) that will be common > for the JMS Session that will consume from ActiveMQ and the JMS Session that > will be publish to TIBCO EMS. > > With the intermediate Queue - I still cannot achieve the above (especially > when I want to group n messages into one transaction - since I want to > achieve high throughput) > > Is there any other work-around any one can recommend? > > regards > D > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/How-to-improve-throughput-by-grouping-messages-in-a-Transaction-tp5773344p5774044.html > Sent from the Camel - Users mailing list archive at Nabble.com.
