It sounds like SJMS may be replaying a transaction. Either that or the
producer and consumer are not using the same JMS Session. Since you’re not
losing messages, I’d guess it’s one of those two scenarios.
I’m not sure if JMS Session Transactions are guaranteed one and only once
delivery - a JMS expert would have to answer that one.
> On Feb 11, 2016, at 1:01 AM, d1x <zdenek.o...@gmail.com> wrote:
>
> Thank you for your answer. I use only one broker, so I don't need that kind
> of XA transaction as you pointed out.
> Anyway setting transacted=true on both consumer and producer does not solve
> the issue as there are always more than 1000 messages in input+output queue
> even there were 1000 messages in input at the beginning.
>
> E.g.
> from("sjms:queue:test-in?transacted=true&consumerCount=5")
> .process(systemOut("Processing"))
> .to("sjms:queue:test-out?transacted=true")
>
> You can try yourself with that simple one-class code...
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/SJMS-transaction-tp5777522p5777570.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
