camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Poltavtsev (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-10505) "FILE" component with option "readLock=rename" throws FileNotFound exception in case of work file is locked/used by another application
Date Tue, 22 Nov 2016 08:44:58 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-10505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrey Poltavtsev updated CAMEL-10505:
--------------------------------------
    Attachment:     (was: diff.txt)

> "FILE" component with option "readLock=rename" throws FileNotFound exception in case
of work file is locked/used by another application
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-10505
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10505
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.17.3
>         Environment: Windows 7 / Java 8.
>            Reporter: Andrey Poltavtsev
>             Fix For: 2.17.4, 2.18.1, 2.19.0
>
>         Attachments: patch.txt
>
>
> Option "readLock=rename" (according to htttp://camel.apache.org/file2.html) is necessary
to lock work file in case of it is not used by another application. But currently we see "FileNotFound"
during test rename operation and "FILE" component tries to lock and process corresponding
work file.
> This issue can be resolved by wrapping of corresponding rename operation by try-catch
block. See patch for "camel-core/src/main/java/org/apache/camel/component/file/strategy/GenericFileRenameExclusiveReadLockStrategy.java"
in attachment which allows to correct current issue.
>   



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message