Component/Node Event Logging Feature - Where in hook a Processor after every component/node to log the message details (an efficient logging mechanism can be in place File/DB/Mongo etc). This is how a savepoint/milestone can be captured, so that on re-start (after crash), you have the intellignce(for DB logging, essentially a query) for finding the messages to recover, from a particular savepoint/milestone to replay to process it further. We have the implementation in our product where in we log in to DB (using DataSource - DBPool - C3P0). We are doing analysis for the feasibility of replacing DB logging with MongoDB, though.
-- View this message in context: http://camel.465427.n5.nabble.com/Failing-over-in-flight-exchanges-tp5725162p5725216.html Sent from the Camel - Users mailing list archive at Nabble.com.
