topic Re: cifs: file locking problem in Alfresco Archive

cifs: file locking problem

spotlight2001 — Fri, 05 Sep 2008 12:09:48 GMT

The problem can be described as follow:1) mount cifs drive, alfresco 2.9cOR alfresco 2.9B(2.9c has the refactored jlan code)2) copy a text file named a.txt to cifs3) edit the textfile with UltraEdit (this is important, because UE creates a BAK file on save; other programs might produce the same effe

Re: cifs: file locking problem

spotlight2001 — Mon, 08 Sep 2008 07:27:52 GMT

thanks for the answer.

There is no hint in the logs, which would shed light on what might cause this.
Basically it boils down to the following "feature": you can only save once per minute on CIFS (within certain applications).

kind regards

Re: cifs: file locking problem

spotlight2001 — Mon, 08 Sep 2008 11:25:31 GMT

the same problem seems to be described also in post http://forums.alfresco.com/en/viewtopic.php?f=4&t=13634&start=0&st=0&sk=t&sd=a&hilit=cifs+lock#p44811

Re: cifs: file locking problem

spotlight2001 — Tue, 09 Sep 2008 18:51:57 GMT

some more interesting(?) details:
* if I rename the parent directory of the locked (i.e. UNREADABLE) file, the locked file can be read.
* if the directory is renamed back to the name it had before, the file is locked again.

I am not sure, but somehow things seem to point to the org.alfresco.jlan.server.filesys.cache package.

This "functionality" severely inhibits productive working with Alfresco CIFS.

Re: cifs: file locking problem

spotlight2001 — Tue, 16 Sep 2008 10:47:45 GMT

I noticed, that a "lock manager" (not sure how it is really called) was introduced in spring 2007 in order to prevent concurrent editing of Word-Dokuments.

I can rather accept concurrent editing (use check-out!) than users not being able editing their own files.

Would it be a correct way to circumvent this problem by commenting out the "lock manager" introduced in 2007 ?

Re: cifs: file locking problem

spotlight2001 — Tue, 16 Sep 2008 20:36:25 GMT

* problem solved by backport of LATEST alfresco 3.0 beta 2 code to 2.9C dev (db schema 118).
* alfresco 3.0 beta 2 was not usable bec. it does NOT run in JBoss (yet)

Alfresco team apparently solved the problems during July acc. to SVN.

A hint like : "we have solved that finally in 3.0 Beta" or similar would have been helpful.

hard work, but definitely the advantages of open source!