Edwin, I'm not sure whether I got your scenario in the right way.
Is it possible to share your route? Do you execute the DB insert/update in
the same thread or asynchronously?
What's with something like:
from("sead:start")
.transacted()
.multicast(aggregationStrategyWhichReturnsTheFirstExchang
Hi Folks,
I have a route that consumes from a seda endpoint, sends the exchange to a
processor and then to jms topic.
I need to persist the message in a DB after I send the exchange to the
processor. After the message has made it to the topic - I take another trip
to the DB to update a status fl
