On Fri, Jul 10, 2009 at 12:51 PM, Leen Toelen wrote:
> Hi,
> thanks a lot for the very detailed feedback. I'll give it a try.
>
The last bit, the warning. What kind of warning do you have in mind?
BTW: Camel itself can also handle redelivery and do all sorts of
tricks in relation to this.
See gen
Hi,
thanks a lot for the very detailed feedback. I'll give it a try.
Regards,
Leen
On Fri, Jul 10, 2009 at 12:42 PM, Claus Ibsen wrote:
> On Fri, Jul 10, 2009 at 11:19 AM, Leen Toelen wrote:
> > Hi,
> > I would like to use an synchronous queueing mechanism, where the
> processing
> > (posting t
On Fri, Jul 10, 2009 at 11:19 AM, Leen Toelen wrote:
> Hi,
> I would like to use an synchronous queueing mechanism, where the processing
> (posting to an HTTP endpoint) is retried muliple times on failure. The retry
> schedule schould be manageable so the retry timer increments and in the end
> a w
Hi,
I would like to use an synchronous queueing mechanism, where the processing
(posting to an HTTP endpoint) is retried muliple times on failure. The retry
schedule schould be manageable so the retry timer increments and in the end
a warning is provided, much like most email servers work. The queu
