You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Jacques Le Roux (JIRA)" <ji...@apache.org> on 2017/05/06 11:01:04 UTC

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

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

Jacques Le Roux commented on OFBIZ-7265:
----------------------------------------

OK done for
trunk r1794132
R16.11 and R15.12 r1794133

No need to svn:ignore, done at a upper level


> 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)