You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by "Karl Wright (JIRA)" <ji...@apache.org> on 2015/01/14 16:17:35 UTC

[jira] [Comment Edited] (CONNECTORS-1145) multiprocess-file-example blocks in configuration on Windows

    [ https://issues.apache.org/jira/browse/CONNECTORS-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277031#comment-14277031 ] 

Karl Wright edited comment on CONNECTORS-1145 at 1/14/15 3:17 PM:
------------------------------------------------------------------

I do not see this on Windows.  Can you be more specific about what connection type you are creating?

Also, please note that file locking is NOT resilient against hard killing of processes.  If you hard-kill any ManifoldCF process, you MUST execute the lock-clean procedure, as outlined on the "how-to-build-and-deploy" page.



was (Author: kwright@metacarta.com):
I do not see this on Windows.  Can you be more specific about what connection type you are creating?

Also, please noted that file locking is NOT resilient against hard killing of processes.  If you hard-kill any ManifoldCF process, you MUST execute the lock-clean procedure, as outlined on the "how-to-build-and-deploy" page.


> multiprocess-file-example blocks in configuration on Windows
> ------------------------------------------------------------
>
>                 Key: CONNECTORS-1145
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1145
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Framework core
>    Affects Versions: ManifoldCF 1.8, ManifoldCF 2.0
>         Environment: Windows 2012
>            Reporter: Andreas Baumann
>
> Saving a configuration setting (for instance a new Output Connector) hangs
> forevert. Inspecting the problem with the 'Process Monitor' shows me
> that there is an infinite loop while locking and reading a file in the syncharea.
> I disabled Windows Search and virus scanners, so far no luck.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)