I do have a suspicion that our underlying problem is more complex as we have had too many marker files being left behind. As the server being polled is running a Microsoft OS there is always the possibility that camel fails to delete the file due to some other process (Virus Scanner, file system indexer etc.) keeping it open. Short lived files tend often to cause problems with virus scanners as the scanner then often keeps the file open when the application tries to delete them. The underlying problem was solved for Unix file systems a long time ago using reference counting inside the file system and core, why MS can't implement something similar still surprises me.
-- View this message in context: http://camel.465427.n5.nabble.com/Problems-with-file-component-tp5752629p5752632.html Sent from the Camel - Users mailing list archive at Nabble.com.
