camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Atanas Shindov <atanas.shin...@gmail.com>
Subject Re: Avoiding duplicate messages
Date Tue, 21 Jan 2014 19:26:27 GMT
Hi Richard,

thanks for your prompt reply.

It looks like the Idempotent Consumer might help, especially if in it's
File/JDBC based implementations the message ids are durably persisted (it
seems quite logical to be so), so that they are available after a JVM
restart for example.

However, the usage of this EIP requires modification of the original route
(insertion of an idempotentConsumer instruction before every destination
endpoint) and I would prefer to use an alternative approach (if it's
possible). 

Does the exchange keep information about which route endpoints have
successfully processed it? Maybe it's the exchange's unit of execution
holding this info?

Thanks again for your help.

Best regards,
Atanas



--
View this message in context: http://camel.465427.n5.nabble.com/Avoiding-duplicate-messages-tp5746278p5746304.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message