ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacques Le Roux (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (OFBIZ-7265) Could not obtain Lock on lucene index Lock
Date Sun, 16 Apr 2017 19:50:41 GMT

     [ 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
         Assignee: Jacques Le Roux
    Fix Version/s: Release Branch 15.12
                   16.11.02
                   Upcoming Release

Thanks a bunch Amardeep, well spotted!

Your solution is in
trunk r1791625  
R16.11 and R15.12 r1791626


> 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, 16.11.02, Release Branch 15.12
>
>
> 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)

Mime
View raw message