[
https://issues.apache.org/jira/browse/OFBIZ-7265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacques Le Roux closed OFBIZ-7265.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: 16.11.02)
(was: Release Branch 15.12)
At r1794771 Jinghai committed for OFBIZ-8316 with this comment
Updated Solr from 6.2.1 to 6.5.1...[snip]...
But unfortunately he reintroduced the path for indexes to /runtime/indexes/products which breaks OFBIZ-7265 on this aspect where I then set it to runtime/indexes/solr to not confuse with Lucene index
I have decide to make things even more clear by using now runtime/indexes/solr/products
I hope nobody will break it again, even if it has no functional impact.
Fixed at revision: 1800453
> 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: lucene
> Affects Versions: Trunk
> Reporter: Jacques Le Roux
> Assignee: Jacques Le Roux
> Priority: Minor
> Fix For: Upcoming Release
>
>
> 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.4.14#64029)
Locked
