Hi Camellers!

During the work on https://issues.apache.org/jira/browse/CAMEL-12668 issue,
I've detected that if custom aggregation strategy is too slow or has a
large delays (~5-10 secs and can be emulated with Thread.sleep), the
default shutdown life-cycle doesn't wait for the aggregation and shutdown
route early and cause RejectedExecutionException.

I understand that in most cases the aggregation with 5-10 seconds is not
permitted and deferred route shutdown could solve the problems but what do
you think about potential investigation in this issue to detect why
shutdown strategy not waiting for route and consumer?

--
Best regards,
Dmitry Volodin

Reply via email to