I think that org.apache.camel.component.file.strategy.MarkerFileExclusiveReadLockStrategy is not thread-safe. It is using the global variable lock and lockFileName to decide which files to delete in the releaseExclusiveReadLock method. That matches the behaviour I'm seeing when only the last file to be read is the one that is deleted after.
-- View this message in context: http://camel.465427.n5.nabble.com/File-component-with-more-than-one-thread-tp3880492p3885874.html Sent from the Camel - Users mailing list archive at Nabble.com.
