Hi Flo, Thanks for putting this together. The timeout is working as expected but I will see if I can make it work with this to create an automated test that handles the aggregation issue.
Thanks again, Scott ES On Mon, Oct 14, 2013 at 2:51 AM, flovansi <florent.vansilie...@swift.com>wrote: > These tests requires manual intervention (looking if messages are still in > the queue or are they committed?). But these are simple tests that proves > the batch transaction support offered by SJMS is not 100% correct > (especially the behaviour of the timeout!!!). > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/SJMS-implementation-Batch-Consumer-tp5741291p5741502.html > Sent from the Camel Development mailing list archive at Nabble.com. > -- -- Scott England-Sullivan Apache Camel Committer Principal Consultant / Sr. Architect | Red Hat, Inc. FuseSource is now part of Red Hat Web: fusesource.com <http://www.fusesource.com> | redhat.com<http://www.redhat.com> Blog: sully6768.blogspot.com Twitter: sully6768