[jira] [Comment Edited] (OFBIZ-7265) Could not obtain Lock on lucene index Lock

[Nicolas Malin (Jira)]

    [ https://issues.apache.org/jira/browse/OFBIZ-7265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15979775#comment-15979775 ]

Jacques Le Roux edited comment on OFBIZ-7265 at 4/22/17 5:32 AM:
-----------------------------------------------------------------

We have though a problem why the lucence indexes location in the solr plugins!

I guess (and IIRW) this is due to some work done to somehow merge functionalities between solr and lucene component. Then we should rather have the indexes at a common level. So I suggest to create them under the global runtime level. I will ask about this on dev ML before creating a Jira. Also svn:ignoring them then will be good thing...


was (Author: jacques.le.roux):
We have though a problem why the lucence indexes location in the solr plugins!

I guess (and IIRW) this is due to some work done to somehow merge functionalities between solr and lucene component. Then we should rather have the indexes at a common level. So I suggest to create them under the global runtime level. I will ask about this on dev ML before creating a Jira.

> 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: Release Branch 15.12, Upcoming Release, 16.11.02
>
>
> 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.15#6346)