I'm dealing with messages, that contain updated values for a certain ID. If such a message can't be processed, it gets redelivered by the activemq broker. In the mean time an other message with newer values for the same id might be enqueued. Since the redelivery delay is quite long it might happen that the newer message gets processed before the older and the whole process isn't in the correct order anymore. In that case, the older message should get discarded to avoid outdated values to override newer values. I thought about an idempotent consumer, but it does not seem to solve the problem because it only tracks IDs but not timestamps. Any help would be appreciated.
-- View this message in context: http://camel.465427.n5.nabble.com/Discard-Obsolete-Messages-After-Redelivery-tp5767439.html Sent from the Camel - Users mailing list archive at Nabble.com.
