camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut-Håvard Aksnes (JIRA) <>
Subject [jira] [Commented] (CAMEL-7525) Behavior change for file component in 2.10 causes problems with no workaround available
Date Fri, 20 Jun 2014 12:25:24 GMT


Knut-Håvard Aksnes commented on CAMEL-7525:

Making the problem even worse for us is that the file system we are monitoring is on a Microsoft
server: File cleanup tend to fail if some other process are reading the file being deleted,
for short lived files this is a huge problem as virus scanners or indexers often keeps the
file open at the time when the delete is attempted.

> Behavior change for file component in 2.10 causes problems with no workaround available
> ---------------------------------------------------------------------------------------
>                 Key: CAMEL-7525
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>            Reporter: Knut-Håvard Aksnes
>  We do use the file component to read files from a particular area. We pick up new files
from there using their content as basis for a database import. There are a couple of important
>  # We must not add or delete files to the area we read from, not even temporarily.
>  # We need to pick up files once.
> To achive this we use noop=true as well as a file based idempotentRepository where the
repository is placed in a different location. We also use readLock=changed which is the big
problem.  To cite the component documentation:
> Notice from Camel 2.10 onwards the read locks changed, fileLock and rename will also
use a markerFile as well, to ensure not picking up files that may be in process by another
Camel consumer running on another node (eg cluster).
> This is a huge problem as I can't find any documented way of storing the marker files
in a different location.  What is really needed is something similar to inProgressRepository
as an option to keep track of the readLock related information. Alternatively an option to
disable the marker files could be created, this option could however lead to failure if applications
are clustered.
> This problem is for us serious breakage, as there are other applications not under our
control reading the same areas, some of these crashes due to the marker files.

This message was sent by Atlassian JIRA

View raw message