[CAMEL-9970] CamelFileLength header is wrong for long write file

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.16.3
• Fix Version/s: 2.18.0
• Component/s: camel-core
• Labels: patch
• Patch Info: Patch Available
• Estimated Complexity: Novice
• Flags: Patch
• Assignee: Claus Ibsen
• Reporter: Sergey Monichev
• Created: 16/May/16 13:30
• Updated: 03/Jul/18 14:41
• Resolved: 20/May/16 07:08

Description

Given a long write file slowfile.dat. Camel polls the file and stores its parameters (length, lastModified...). Camel tries to get exclusive read lock and fails as file is writing by someone, next time Camel gets lock. But file was changed and its parameters are wrong.
The solution is pretty simple - check the file length and lastModified when exclusive read lock is granted and update them.

Here is a patch: http://pastebin.com/2vyF8BTU

Issue Links

• causes: CAMEL-12613 Camel file endpoint loses modification date and length information when preMove is used