One thing to keep in mind when you are experiencing odering issues is
that you can use ActiveMQ's message groups to make all messages for
one group to the same consumer. Very often that little trick helps
and still allows some form of concurrency for different groups.
Andreas
On 09/05/2013
+1 Andreas' comment.
So what i was thinking was something like this...
from(ibmmq1).to(seda:stage)
from(ibmmq2).to(seda:stage)
from(ibmmq3).to(seda:stage)
from(seda:stage?concurrentConsumesr=1).to(direct://buzComponent)
On Fri, Sep 6, 2013 at 3:57 AM, Andreas Gies
Thanks a lot!
It just worked.
On Fri, Sep 6, 2013 at 10:34 PM, Christian Posta
christian.po...@gmail.comwrote:
+1 Andreas' comment.
So what i was thinking was something like this...
from(ibmmq1).to(seda:stage)
from(ibmmq2).to(seda:stage)
from(ibmmq3).to(seda:stage)
Hi,
Camel was wonderful piece of software and using it in production for more
than a year. Our version of Camel was 2.10.1
I recently added few additional route (and bug in buz logic too) to
interface with additional systems, all the routes are doing the similar
job. They read JMS message from
So what's the underlying concurrency issue? Ordering? Can you just have a
route that multiplexes all of those incoming queues into a single queue (or
in-mem queue) and then have a route w/ only one thread that does CBR and
invoke the correct bean?
On Thu, Sep 5, 2013 at 9:02 AM, gnani swami
Some of the messages where handled by wrong service and they are all queued
in FailedErrorMessages directory. Application failed to process them. So it
will end up in ordering, and lost message. Looking at our various
exception it is quite easy for us to understand that they are caused by
