Hello,
we noticed an issue in our production system where AggregateRecoverChecker
produces duplicates.
It seems that the cause for this issue was that we initially had the
/useRecovery/ configuration disabled. Then at a later release we enabled the
recovery functionality and on application
Hello,
you need to define a custom type converter to convert from String to the
type that you want. Check the documentation for type conversion here:
http://camel.apache.org/type-converter.html
--
View this message in context:
Hey Carl,
you can define a custom processor to throw an exception whenever you want:
weaveById("ws-call").replace().processor(new Processor {
@Override
void process(Exchange e) {
// Some custom logic in here to throw an exception
}
});
--
View this message in
Hey Zoran,
I didn't use SmartLifeCycle for a particular reason, it was just a leftover
of trying stuff :).
As for the fix in the PR I tried it and it didn't work, I see the same
behaviour as with the workaround without the loop. Here are some logs:
16:58:32.026 [Thread-3] INFO
Hello Zoran,
thank you for the input it was really helpful. I tried it and although I can
see that now the camel context definately shuts down first, the other beans
are still shut down before camel context is closed probably because the
shutdown of routes happen asychronously. What I ended up
Hello,
I am using camel 2.18.2 with camel spring boot starter and spring versions:
1.4.1.RELEASE
4.3.3.RELEASE
We consume messages from a kafka component and we shutdown the application,
some beans are destroyed before the CamelContext causing messages to be lost
because either e seda component
