camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (CAMEL-1195) File component - exclusive read lock strategy using renaming
Date Thu, 25 Dec 2008 08:57:05 GMT

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

Willem Jiang reopened CAMEL-1195:
---------------------------------


Hi Claus,
I tried to fix the test error of FileExclusiveReadRenameStrategyTest in some no windows box,
but no luck. 
So I reopen this issue and commented out the failed test cases.
Could you take a look at this when you have time ?

Merry Christmas :)

Willem

FileExclusiveReadRenameStrategyTest.testPollFileWhileSlowFileIsBeingWritten  (org.apache.camel.component.file)
    java.lang.AssertionError: mock:result Expected minimum 3000 millis waiting on the result,
but was faster with 899 millis.
    at org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:746)
    at org.apache.camel.component.mock.MockEndpoint.waitForCompleteLatch(MockEndpoint.java:721)
    Show details »
    « Hide details
    java.lang.AssertionError: mock:result Expected minimum 3000 millis waiting on the result,
but was faster with 899 millis.
    at org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:746)
    at org.apache.camel.component.mock.MockEndpoint.waitForCompleteLatch(MockEndpoint.java:721)
    at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:238)
    at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:218)
    at org.apache.camel.component.file.FileExclusiveReadRenameStrategyTest.testPollFileWhileSlowFileIsBeingWritten(FileExclusiveReadRenameStrategyTest.java:76)
    « Hide details 

First failed in build #1611
with 2 changes FileExclusiveReadRenameStrategyTest.testPollFileWhileSlowFileIsBeingWrittenWithTimeoutAndNoop
(org.apache.camel.component.file)
    java.lang.AssertionError: mock:result Expected minimum 3000 millis waiting on the result,
but was faster with 1003 millis.
    at org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:746)
    at org.apache.camel.component.mock.MockEndpoint.waitForCompleteLatch(MockEndpoint.java:721)
    Show details »
    « Hide details
    java.lang.AssertionError: mock:result Expected minimum 3000 millis waiting on the result,
but was faster with 1003 millis.
    at org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:746)
    at org.apache.camel.component.mock.MockEndpoint.waitForCompleteLatch(MockEndpoint.java:721)
    at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:238)
    at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:218)
    at org.apache.camel.component.file.FileExclusiveReadRenameStrategyTest.testPollFileWhileSlowFileIsBeingWrittenWithTimeoutAndNoop(FileExclusiveReadRenameStrategyTest.java:125)
    « Hide details 



> 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