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 <ja...@les7arts.com> on 2016/06/07 08:55:26 UTC

Lucene index Lock

Hi,

Should we worry about this message I found in error.log?

2016-06-07 10:35:23,327 |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

I tested indexing contents and products works w/o pb.

Jacques

Re: Lucene index Lock

Posted by Jacques Le Roux <ja...@les7arts.com>.

Thanks Jacopo,

I'll create a Jira using your answer as description

Jacques


Le 08/06/2016 � 15:08, Jacopo Cappellato a �crit :
> 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.
>
> Jacopo
>
>
>
> On Tue, Jun 7, 2016 at 10:55 AM, Jacques Le Roux <
> jacques.le.roux@les7arts.com> wrote:
>
>> Hi,
>>
>> Should we worry about this message I found in error.log?
>>
>> 2016-06-07 10:35:23,327 |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
>>
>> I tested indexing contents and products works w/o pb.
>>
>> Jacques
>>
>>
>>
>>

Re: Lucene index Lock

Posted by Jacopo Cappellato <ja...@hotwaxsystems.com>.

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.

Jacopo

On Tue, Jun 7, 2016 at 10:55 AM, Jacques Le Roux <
jacques.le.roux@les7arts.com> wrote:

> Hi,
>
> Should we worry about this message I found in error.log?
>
> 2016-06-07 10:35:23,327 |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
>
> I tested indexing contents and products works w/o pb.
>
> Jacques
>
>
>
>