You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2009/07/07 16:44:08 UTC
[jira] Commented: (CAMEL-1808) file component - markerFile read
lock - do not use nio FileLock
[ https://issues.apache.org/activemq/browse/CAMEL-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52721#action_52721 ]
Claus Ibsen commented on CAMEL-1808:
------------------------------------
See forum
http://www.nabble.com/Apache-Felix-Karaf-must-be-restarted-to-remove-lock-on-a-file--consumed-in-a-camel-route-td24368909s22882.html
> file component - markerFile read lock - do not use nio FileLock
> ---------------------------------------------------------------
>
> Key: CAMEL-1808
> URL: https://issues.apache.org/activemq/browse/CAMEL-1808
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.0-M2
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.0.0
>
>
> In some situations in OSGi platforms the file lock can be kept and then you need to shutdown the JVM to clear the JDK FileLock.
> So better to not use them as we can just create the file and Camel will still back off reading the file as it can see the lock file exists.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.