I can avoid this issue by throttling the file polling by adding the following options to the file uri:
initialDelay=3000&delay=1000&maxMessagesPerPoll=20. It seems that the exception occurs in one of the following two situations: 1. When Camel polls the folder immediately after being started while there are many files in the folder. The increase of initialDelay seems to help. 2. When Camel polls more new files while previously polled files have not been processed completely. If anyone can shed some light on this, that would greatly appreciated. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-retries-a-message-after-the-message-has-been-completed-successfully-tp5731930p5732044.html Sent from the Camel - Users mailing list archive at Nabble.com.
