[
https://jira.nuxeo.org/browse/NXP-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=84731#action_84731
]
Thierry Martins commented on NXP-6000:
--------------------------------------
I've also noticed a similar problem which happens systematically when Nuxeo DM
is launched in debug mode (do not happen under Linux)
> "Cannot open fulltext index" at startup
> ---------------------------------------
>
> Key: NXP-6000
> URL: https://jira.nuxeo.org/browse/NXP-6000
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Affects Versions: 5.4
> Environment: WindowsXP
> Reporter: Youri Ginieys
>
> During startup, on my dev box (WindowsXP), there are often lucene related
> errors :
> 10:59:09,019 ERROR [H2Fulltext] Cannot open fulltext index
> org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out:
> simplefsl...@c:\nuxeo-dm-5.4.0-tomcat\nxserver\data\h2\nuxeo.lucene\write.lock
> at org.apache.lucene.store.Lock.obtain(Lock.java:85)
> at org.apache.lucene.index.IndexWriter.init(IndexWriter.java:692)
> at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:453)
> at
> org.nuxeo.ecm.core.storage.sql.db.H2Fulltext.getIndexWriter(H2Fulltext.java:410)
> at
> org.nuxeo.ecm.core.storage.sql.db.H2Fulltext.access$100(H2Fulltext.java:58)
> at
> org.nuxeo.ecm.core.storage.sql.db.H2Fulltext$Trigger.init(H2Fulltext.java:607)
> When this happen, any document creation fails.
> Stop NuxeoDM, manual deletion of the write.lock and start again solves the
> issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
