On Di, 2013-11-05 at 14:30 -0500, France Baril wrote:
This Issue occurs when the server stops while files are open/locked:
When basex starts it doesn't show lock icons on files the user had locked before the server stopped.
When users tries to open a file oxygen says the file is locked, even though the current user owns the lock. In other words, the lock seems to be tracking something that doesn't survive sessions.
Unfortunately, I couldn't reproduce this behavior. When I restart the server, I can still open files which I have previously locked in oxygen. The only case when one can have such behavior is the following:
1. user1 locks doc.xml -> lock1 2. server goes down 3. lock1 expires in 5 min 4. server comes up 5. user2 locks doc.xml -> lock2 6. user1 cannot lock doc.xml
However, this scenario describes correct behavior.
It would be helpful to send some debug data, e.g. setting the DEBUG [1] option and providing the process console output and logs [2]. Most appropriately would be, of course, if you could provide a small detailed use case which triggers the problem.
To recover, we delete the webdav db + restart Oxygen.
Granted, doing all check-ins prior to stopping the server for maintenance would be a best practice. But in case of an unexpected failure, since the lock are saved in ~webdav, is there anyway we could get back to the locks as set in ~webdav?
If the locks have not expired, they will be considered even after restart of the server.
Best regards, Dimitar
[1] http://docs.basex.org/wiki/Options#DEBUG [2] http://docs.basex.org/wiki/Logging