[
https://issues.apache.org/activemq/browse/CAMEL-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52072#action_52072
]
Claus Ibsen commented on CAMEL-1670:
------------------------------------
Hi Joe
I assume its the *trunk* you try? As 2.0m1 is 2 months old.
Could you try different combinations of the *readLock* on the file endpoint.
See this wiki page for possible values:
http://camel.apache.org/file2.html
And also try with *noop=true* instead of *move=endDirectory* to avoid the last
move operation.
All in all to help pin point where Windows have a problem with lock files.
And could you paste the stacktrace.
> thread() and File Components
> ----------------------------
>
> Key: CAMEL-1670
> URL: https://issues.apache.org/activemq/browse/CAMEL-1670
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.0-M1
> Environment: Microsoft Windows XP
> Reporter: Joe Gottman
>
> I just experimented with adding calls to thread(10) to my route to make it
> multithreaded. This definitely speeds up by route, but it keeps throwing
> java.nio.channels.OverlappingFileLockException errors and leaving lock files
> behind it. The start of my route looks like
>
> from("file:\\startDirectory?move=endDirectory")
> .threads(10)
> .bean("myBean", "myMethod")
> Afterwards, my route ran successfully but an OverlappingFileLockException was
> thrown for every file that was read and all the lock files were left in my
> source directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
