You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Jacques Le Roux (JIRA)" <ji...@apache.org> on 2016/06/09 09:38:20 UTC
[jira] [Created] (OFBIZ-7265) Could not obtain Lock on lucene index
Lock
Jacques Le Roux created OFBIZ-7265:
--------------------------------------
Summary: Could not obtain Lock on lucene index Lock
Key: OFBIZ-7265
URL: https://issues.apache.org/jira/browse/OFBIZ-7265
Project: OFBiz
Issue Type: Bug
Components: specialpurpose/lucene
Affects Versions: Trunk
Reporter: Jacques Le Roux
I found this message in error.log
|xer_default_products |DocumentIndexer |E| Could not obtain Lock on lucene index Lock held by this virtual machine: C:\projectASF-Mars\ofbiz\runtime\indexes\products\write.lock
Here is Jacopo's answer:
bq. We should not worry (because the "lucene" component is just an experimental one) but let's keep an eye on it: it is caused when two threads are trying to update documents in the Lucene index; it may happen when two events modify data that trigger the execution of the document update. We could consider to enhance the DocumentIndexer to properly manage these scenarios.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)