[CAMEL-3793] Try to copy file when rename fails

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.8.0
• Component/s: camel-core

Environment

Linux with NFS mounted directory pointing to a Windows 2008 Server shared directory

• Assignee: Claus Ibsen
• Reporter: Jean-Michel Morel
• Created: 21/Mar/11 13:16
• Updated: 01/Oct/11 15:20
• Resolved: 01/May/11 10:44

Description

I have a setup where I use file component to move files after being processed ou when processing fails.
As I have no troubles neither on my development workstation neither on local directory on my linux environnement. It fails when the monitored directory is a NFS mounted directory pointing to a Windows 2008 Server shared directory.
While it's not a camel bug, the generated logs are just useless because we can't get the reason of failure.

Investigating the source code tells me that the File.renameTo method is used (with the three times try hack for Windows , so I can't get any further information on the reason.

Could you implement a fallback strategy like copy the file and delete the original one ? (should it be made optional)

To workaround this, I currently do the move operations manually by invoking the FileUtils.moveTo(...) from commons-io (which implements exactly the fallback method I described on renameTo failure).
But, I have side effects as I'm forced to use the noop attribute.
(in fact, it doesn't explain why the rename fails, but it works, and should it be a failure I'll get an explicit error message).

Issue Links

• relates to: CAMEL-2058 File Component - Rename operations fail sometimes on certain filesystems (Windows)
• relates to: CAMEL-4505 FileUtils change to make 'copy/delete instead of renaming' feature configurable