A Camel route uses a file: endpoint to read files from an NFS-mounted directory. The same directory is read by multiple, identical instances of the Camel route in different processes.
With the default file locking behaviour (markerFile) multiple instances can read the file, leading to duplicate processing. When this happens, an exception is seen relating to renaming files (attached).
) thread #0 - file:///mnt/tmp/] GenericFileOnCompletion WARN Error during commit. Exchange[Message: Hello]. Caused by: [org.apache.camel.component.file.GenericFileOperationFailedException - Cannot rename file: GenericFile[/mnt/tmp/20] to: GenericFile[/mnt/tmp/.camel/20]]
org.apache.camel.component.file.GenericFileOperationFailedException: Cannot rename file: GenericFile[/mnt/tmp/20] to: GenericFile[/mnt/tmp/.camel/20]
at org.apache.camel.component.file.strategy.GenericFileProcessStrategySupport.renameFile(GenericFileProcessStrategySupport.java:115)
at org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:88)
- relates to
-
ENTESB-3880 Create file-master component which acts like the fabric master component but uses file locks instead of ZK locks
-
- Closed
-
