Hi Yes the resequencer is memory based, and it is NOT possible to make it part of a transaction.
On Fri, May 8, 2015 at 6:28 AM, amit2103 <ami...@nrifintech.com> wrote: > Hi, > > My scenario is that I have 1 jms queue, from which I read with concurrent > consumeres, use resequencer and a message header to arrange the messages > and then send them to another queue. > > Our route is transacted. Now does the sending part happen in a transaction. > It seems to me that although the processor is transacted, when resequncer is > applied, the sending part is not transacted. As a result for a very short > period of time, the messages are in memory yet not send to the other queue. > > is my assumption correct, is there any way to make the whole process > transacted. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Resequencer-and-JMs-transactions-tp5766843.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
