Hi all,
My client, is using eXist *1.4.1 *as their content database, they have a lot
of xml files for editing. They use Oxygen XML editor's Data Source Explorer(
I assume it is through Webdav), they also enabled the lock-mechanism in
eXist, so whenever a user has access to a file, then other user will be able
to see a lock on that and won't be able to access it, which worked fine in
the past few months. Recently, they reported to me that the database kept
crashing recently, especially when some editors were trying to open some
particular xml files, and after crashing, the lock still remain there even
after restarting eXist. If they try to access that file again, it will
prompt the following warning message:
*"Problem while trying to acquire the lock": *
*423 Locked for*
*http:....*
*Depth:0*
*Owner:mduross*
*Token:*
*
*
*If the current lock expires during editing you could overwrite changes made
by the current lock owner.*
*It is strongly recommended to cancel the open operation.*
The only that I know that they did to the database file is having a
re-index, other than that, nothing has been tampered with recently. So I am
clueless to where to troubleshoot at this stage. They sent me the log file,
but I don't know where to look at either.
I would be really really grateful if experts could offer some advice or
suggestions for me to take further research. Thanks a lot !!
Robert
|