Support for concurrent file consumers on NFS with SwitchYard/Camel File component
A Camel route that starts with a
file: endpoint looks at an NFS-mounted directory. There are several instances of the Camel host (Fuse, EAP) on different physical hosts, all looking at the same mount, and all competing for the same files. With small throughputs everything is OK but, if a large number of files are placed into the directory, we get problems. Sometimes the files get read by more than one process (and so end up as duplicate Camel messages); Sometimes the marker files don't get deleted when they should; sometimes files don't seem to get read at all; sometimes we get exceptions because Camel scans the directory to find which files to read and then, when it goes to read them, they've already been read and deleted by a different process.
File2 component actually support this mode of operation?
Same situation occurs with
SwitchYard application too. Does
SwitchYard support this mode of operation?
- Red Hat JBoss Fuse Service Works (FSW)
- Red Hat JBoss Fuse
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.