camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-1195) File component - exclusive read lock strategy using renaming
Date Fri, 26 Dec 2008 10:37:05 GMT

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

Claus Ibsen resolved CAMEL-1195.
--------------------------------

    Resolution: Fixed

Thanks for the reports.

I have commited a fix that only runs the tests on Windows.

This strategy is hard to test on other file systems as it behaves differently and something
is not possible from within the same JVM such as creating a new file and having locks on it
while from the same JVM trying to get a lock waiting for the other to finish. This is really
only possible from separate JVM's

> File component - exclusive read lock strategy using renaming
> ------------------------------------------------------------
>
>                 Key: CAMEL-1195
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1195
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.5.0, 1.5.1
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.0.0
>
>
> See CAMEL-760
> But an end user has problem with this, the read lock can not be granted and a IOException
is thrown.
> We should support the same strategy as the FTP consumer does with a try to rename the
file.
> Also we should allow some nice URI options to select the strategy
> - nio locks
> - renaming

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message