Delayed Retry over several days

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Delayed Retry over several days

Michael R.
Dear Camel Specialists,

i am looking for the best option for the following use case:

We have a lot of big messages (100 MB- 1GB) in one flow.
How can we implement a retry mechanism that tries to retry over several
days.
*But without blocking* the other messages in the JMS (Artemis).

Are there any best practises you can share with us?

Flow:
from(Source (File)).to(jms)

from(jms).process(some data conversion with possible retryable errors)
to(jms)

from(jms).to(file//target)

Thanks in advance.
 Michael
Reply | Threaded
Open this post in threaded view
|

Re: Delayed Retry over several days

Claus Ibsen-2
Hi

Since its so many days then you may have a 2nd queue as "dead letter"
and move the fault JMS message to this. And then have another route /
scheduled logic etc that periodically moves message back to the input
queue so they can be retried.


On Tue, Jul 28, 2020 at 10:42 AM Michael Rambichler
<[hidden email]> wrote:

>
> Dear Camel Specialists,
>
> i am looking for the best option for the following use case:
>
> We have a lot of big messages (100 MB- 1GB) in one flow.
> How can we implement a retry mechanism that tries to retry over several
> days.
> *But without blocking* the other messages in the JMS (Artemis).
>
> Are there any best practises you can share with us?
>
> Flow:
> from(Source (File)).to(jms)
>
> from(jms).process(some data conversion with possible retryable errors)
> to(jms)
>
> from(jms).to(file//target)
>
> Thanks in advance.
>  Michael



--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2