Hello, zagirova.
Thierry Delprat has answered you on the mailing list (it's not visible in the
forum). I copy his mail here:
{code}
Hi,
The write.lock is used by lucene index for H2 database.
The lock file may remain :
- if you shut down the server in middle of a transaction
- if you do concurrent access
- if you have a buggy plugin
- if you use windows and have a virus scanner that locks lucene files
This lock problem only exist with the test backend based on H2 database, with
PGSQL or Oracle you won't have such issues.
This means :
- don't use H2 to do load testing or concurency tests
- don't use H2 for production !!!
To be completely fair, the issue is not really H2, but the fulltext indexing
for H2 that is provided by lucene.
This problem could probably be fixed, but it's good to have this limitation
because it prevent people from using the default embeded DB in production !
(this DB is here only for simple testing and dev mode).
Tiry
{code}
--
Posted by "enriqueperez" at Nuxeo Discussions <http://nuxeo.org/discussions>
View the complete thread:
<http://www.nuxeo.org/discussions/thread.jspa?threadID=4348#13421>
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
To unsubscribe, go to http://lists.nuxeo.com/mailman/options/ecm
