Owain, That's why my preference would be to use the chron job he mentioned and just check my own timestamp in millis in a header or even putting the items in a map and putting that on the queue. The map would have number of retries, timestamp, and the actual data model he's working with. That would keep it relatively simple and performant if not the most elegant solution on the planet.
On Thu, Nov 3, 2016 at 1:37 PM, owain <owain@integration.technology> wrote: > Just be careful of using the Active MQ delay since unless you clean this > header up, it propagates to every subsequent queue. Quite difficult to > debug! > > > > -- > View this message in context: http://camel.465427.n5.nabble. > com/Best-way-to-build-a-wait-retry-loop-with-Camel-tp5789712p5789722.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
