Hello, I'm currently facing an issue when using the Aggregator component in a processing flow. The processing flow is as follows :
|-------------------------------| | Main route entry point | | Split | | Content based router | |--------------------------------| _________________________|____________________________ | | | | |-----------------------------| |-----------------------------| |--------------------| ... | Route 1 entry point | | Route 2 entry point | | route 3 | | Aggregate on key | | Aggregate on key | | same | |------------------------------| |------------------------------| |---------------------| | | | | -------------------------------------------------------------------------------------------- | |-------------------------------------| | Last step, common | | Processing, persist in DB | |---------------------------------------| When an Exception occurs in the last step, it bubbles up and is swalloed by the Aggregator step. From what I sow in debug, the Aggregator is using an ExceptionHandler which is the LoggingExceptionHandler whose purpose is .... to log the exception. >From what I saw, there is another ExceptionHandler, the BridgeExceptionHandlerToErrorHandler. This one seems to be the one generally used by other components to allow the exceptions to go into the Camel routing engine. Is there any way to get the aggregator behave as it should ? Meaning to let the exception bubble up to the main route, such that rollback operation (file move to error folder, for example), can occur. Thank you very much in advance for your support ! Regards, Laurent Laurent Lamouline +32 491 10 96 10 laur...@konekto.be https://www.konekto.be This communication may contain confidential and/or otherwise proprietary material. If you are not the intended recipient, please immediately notify the sender and destroy the original e-mail and any attachments.