You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Ruwan Linton (JIRA)" <ji...@apache.org> on 2009/08/08 20:55:14 UTC
[jira] Commented: (SYNAPSE-565) VFS transport should support a
locking mechanism
[ https://issues.apache.org/jira/browse/SYNAPSE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740942#action_12740942 ]
Ruwan Linton commented on SYNAPSE-565:
--------------------------------------
Implemented the locking... I think it has to be configurable and should be able to turn off locking to achieve performance on a deployment where there cannot be a conflict.
Planning to implement it before resolving the issue.
Now before processing any file vfs listener will create a lock and it will be removed just after completing the processing, so no two listeners will process the file at the same time.
Also before starting to upload a file the sender creates a lock file so the VFS listener will not process that file until the file is fully uploaded and the lock is removed. Bot the listener and the sender treats a file item lock as a file with the same name suffixed by the ".lock" sub string.
> VFS transport should support a locking mechanism
> ------------------------------------------------
>
> Key: SYNAPSE-565
> URL: https://issues.apache.org/jira/browse/SYNAPSE-565
> Project: Synapse
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 1.2
> Reporter: Ruwan Linton
> Assignee: Ruwan Linton
> Fix For: 1.3
>
>
> For more information please refer to;
> https://wso2.org/jira/browse/ESBJAVA-602
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org