Hi Christian
handled(false) is ought to go back to the initial consumer which is
direct:start. Do you know why I never the less get following warn log output
and how I can get rid of it?
WARN -org.apache.camel.processor.aggregate.AggregateProcessor:Error
processing aggregated exchange... followed
Given following blueprint snippet:
How can I modify the blueprint.xml (or the test) if I'm only interested in
testing route two without the need to setup an activemq broker?
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-test-a-si
Given following blueprint and camel context:
amq: and PlatformTransactionManager are available in Fuse, the route works
as expected.
How ca
Hi Willem
Thanks for your answer!
This filter should be able to skip out-of-order messages having the same
correlation id but an older timestamp in a persistent manner, that's why I
thought about a FileIdempotentRepository but this repo cannot track an id
and a timestamp in conjunction. Is there
I'm dealing with messages, that contain updated values for a certain ID. If
such a message can't be processed, it gets redelivered by the activemq
broker. In the mean time an other message with newer values for the same id
might be enqueued. Since the redelivery delay is quite long it might happen
