akshaydharphale / ganttproject

Automatically exported from code.google.com/p/ganttproject
0 stars 0 forks source link

WebDAV lock is not released #12

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Copied from the bug tracker on SourceForge:
https://sourceforge.net/tracker/index.php?func=detail&aid=1119232&group_id=72728
&atid=535427

Problem: if I open a project from a webdav server and
then Quit
GanttProject, the exclusive lock is not released (the
UNLOCK command is
never sent to the server). If I close the project
window (which
automatically quits GanttProject), the UNLOCK command
is sent.

The problem does not occur for 1.10.3 running under
GNU/Linux:

Original issue reported on code.google.com by dbarashev on 1 Dec 2008 at 12:31

GoogleCodeExporter commented 9 years ago
It is likely that this problem was fixed in GP 2.0.6, but I didn't verify it

Original comment by dbarashev on 1 Dec 2008 at 12:33

GoogleCodeExporter commented 9 years ago
hi,

First of all I thank the contributors for the wonderful tool.

We are facing a similar issue on GP 2.0.9 
mod_dav with Apache running on Ubuntu.
Ganttproject Client: OSX and Windows

As soon as we open a project, the LOCK gets set and cannot save the changes made
after(because the lock is still there). The Lock gets released when we quit the
application.

On further investigation, I found out the param "LOCK WebDAV resources" under
settings which was set to 240min by default. The minimum time limit I can set 
is 1
minute. Using this configuration, I can do operations like open, save etc at the
intervals of atleast 1 min of the preceding operation. Correct me if I am 
wrong, but
should the lock exist till 1 min (minimum time) after the project is opened or 
saved.
I am wondering if this is the expected behavior? 

Any help/clarification/comment on the above issue would be helpful.
Thanks again,
Kunal

Original comment by kgm...@gmail.com on 21 May 2009 at 7:49

GoogleCodeExporter commented 9 years ago
hi,

First of all I thank the contributors for the wonderful tool.

We are facing a similar issue on GP 2.0.9 
mod_dav with Apache.
Ganttproject Client: Windows

have tried to put the "LOCK WebDAV resources" to 1 mn. does not work!!!!
once, I got the block error message, even a local save file produce the same 
error.

What is the solution??

Best regards

Original comment by Quoniam....@gmail.com on 18 Jul 2009 at 5:36

GoogleCodeExporter commented 9 years ago
This behaviour still persist in version 2.0.10: PROPFIND fails and then the LOCK
fails (not because of another lock, but because the file it is trying to lock 
does
not exist).

Original comment by miguel.b...@calzavara.it on 24 May 2010 at 3:58

GoogleCodeExporter commented 9 years ago
I have the same problem - cannot save anything to my project located at WebDAV 
server because it is locked. 
GP 2.0.10
Error Message: 
http://s3.amazonaws.com/floomby/10_4_2010/A9tZei25pU635UlY1SGqQ.jpg

Original comment by dmitry21csm on 4 Oct 2010 at 2:46

GoogleCodeExporter commented 9 years ago
I have the same problem in 2.0.10 for mac os 10.6. Same error message as 
dmitry21csm. Webdav is so close... but not useable.  Anything we can do to help?

Original comment by uncleber...@gmail.com on 12 Nov 2010 at 9:53

GoogleCodeExporter commented 9 years ago
I do not exactly know the reason why it fails for you guys, but I had some 
similar problems (I think) and fixed it with revision 
9c0cb3c852a4853c41e165fe6d02801b8346af16.

So please try the next (beta) version (or compile this release or newer) and 
report back whether it solved your problems or not.

Original comment by maarten....@gmail.com on 22 Jul 2011 at 12:41

GoogleCodeExporter commented 9 years ago
Still does not work:

Steps which fail for me:
1. New project
2. Open from http://127.0.0.1/testGantt.xml, username, password, lock, 5 minutes
3. Directly save to server

I get: "The specified path is currently locked. Please select another path"

After that a 'local save' dialog opens (which might be another bug..?)

Original comment by maarten....@gmail.com on 24 Jul 2011 at 2:35

GoogleCodeExporter commented 9 years ago
3. Directly save to server  -- do you press "Save" or use "Web Server => Save 
to server" ?

Original comment by dbarashev on 24 Jul 2011 at 8:56

GoogleCodeExporter commented 9 years ago
I used "Web Server => Save to server", I did *not* try to use "Save" to save a 
remotely opened document

Original comment by maarten....@gmail.com on 24 Jul 2011 at 10:06

GoogleCodeExporter commented 9 years ago
I think r7ca3e591f840 fixes the last case.

Original comment by dbarashev on 3 Aug 2011 at 11:50

GoogleCodeExporter commented 9 years ago
Yes, it fixes the problem for me

Original comment by maarten....@gmail.com on 4 Aug 2011 at 12:21

GoogleCodeExporter commented 9 years ago
Issue 191 has been merged into this issue.

Original comment by dbarashev on 4 Aug 2011 at 9:21

GoogleCodeExporter commented 9 years ago
Issue 315 has been merged into this issue.

Original comment by dbarashev on 26 Oct 2011 at 8:54

GoogleCodeExporter commented 9 years ago

Original comment by dbarashev on 22 Sep 2014 at 12:22