Hi
A good approach could be to design your applications to detect
duplicate messages.
See the idempotent consumer.
http://camel.apache.org/idempotent-consumer.html
That is much easier than trying to have a high QoS of delivering a
message exactly once.
That is frankly very hard as you need tight
It won't resume where it left off by default. Camel will only delete the
file if it was successfully processed and when it fails, the portion already
send to AMQ will not be rolled back. When the process resumes, it will
process the entire file again. One option is to use the file's moveFailed
o
