Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-2851

Camel file component does not lock properly when consuming from an NFS4 mount

XMLWordPrintable

    • 0
    • 0% 0%
    • Todo
    • Resolving as not a bug. Enhancement issue opened.
    • 7.0 Sprint 1

      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)

        1. camellock.zip
          5 kB

          There are no Sub-Tasks for this issue.

              hchirino Hiram Chirino
              rhn-support-kboone Kevin Boone
              Tomas Turek Tomas Turek
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: