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 another approach to store an id and a timestamp or is messaging the wrong technique for that problem and I should consider switching to a JPA based approach? -- View this message in context: http://camel.465427.n5.nabble.com/Discard-Obsolete-Messages-After-Redelivery-tp5767439p5767458.html Sent from the Camel - Users mailing list archive at Nabble.com.
