I use RecipientList with a custom Aggregator. If there is an error in a
sub-route (one of the "recipients") that is "handled" there.
I want the main route to continue
In the Aggregator, I was setting:
if (oldExchange == null) {
oldExchange = newExchange;
}
Because of this, the Exchan
I use RecipientList with a custom Aggregator. If there is an error in a
sub-route (one of the "recipients") that is "handled" there.
I want the main route to continue
In the Aggregator, I was setting:
if (oldExchange == null) {
oldExchange = newExchange;
}
Because of this, the Exchan
Thanks for your reply ;
I forgot to mention that this circuit represents a workflow : when a message
comes from q1, it has to follow the steps in order to avoid data inconsistency.
Your proposition is good if we can do something like :
from(jms:queue:q1).dynamicRouter().method(DynamicRouterTest.c
Hi Damien,
from("jms:queue:queue1") reads messages once at a time.
Using from("jms:queue:q1?concurrentConsumers=2") may help but imply
consequences in terms of resources, thread safety, readability...
In such a situation, I would avoid reusing q1 if possible. For instance,
you may be able to
I have several Camel routes defining a "circuit" like this (where `qx` is
the queue number x, `px` is the processor number x)
q1 -> p1 -> q2 -> p2 -> q1 -> p1 -> q3 -> p3 -> (...)
as
from("jms:queue:q1).process("p1").dynamicRouter().method(DynamicRouterTest.class,
"nextStep");
from("jms
