Hey Mark,

We ended up opting to put the message back on the end of the queue instead of rolling back, but this leads to repeated reprocessing of the message. My guess is that you have solved this with metadata:

Our framework is sophisticated enough to
manage redeliveries in this way by adding some redeliveredCnt metadata to
the message each time it is cloned.

Can you elaborate?

Thanks,
Geoff.

Reply via email to