Hello,
I'm trying to use the File component that comes with Camel 2.6.0 and I'm
having 2 different problems based on whether I'm using "markerFile" or
"fileLock" as a readLock strategy.
If I use the default (markerFile), there are files being left behind after
they have been processed. The files
I forgot to mention I'm using Linux.
Thanks,
Maria Iracheta
--
View this message in context:
http://camel.465427.n5.nabble.com/File-component-with-more-than-one-thread-tp3880492p3882888.html
Sent from the Camel - Users mailing list archive at Nabble.com.
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 t
Hi,
I think that MarkerFileExclusiveReadLockStrategy is not thread-safe. When I
run a File endpoint with more than one thread the
MarkerFileExclusiveReadLockStrategy only deletes the last file to start
being processed.
The MarkerFileExclusiveReadLockStrategy uses global variables:
private File l
