On Thu, 6 Jan 2005, Erik Hatcher wrote:
>
> On Jan 6, 2005, at 10:41 AM, Joseph Ottinger wrote:
> > SHouldn't Lucene warn the user if they do something like this?
>
> When a user indexes a null? Or attempts to write to the index from two
> different IndexWriter instances?
>
> I believe you should
On Jan 6, 2005, at 10:41 AM, Joseph Ottinger wrote:
SHouldn't Lucene warn the user if they do something like this?
When a user indexes a null? Or attempts to write to the index from two
different IndexWriter instances?
I believe you should get an NPE if you try index a null field value?
No?
Well, I think I isolated the problem: stupid error on my part, I think. I
was adding an indexed field that had, um, a value of null. Correcting that
made the process go much more properly - although note that I haven't
scaled up to have multiple elements to index. Good milestone, though.
SHouldn't
Do you have two threads simultaneously either writing or deleting from
the index?
Erik
On Jan 6, 2005, at 9:27 AM, Joseph Ottinger wrote:
Sorry to reply to my own post, but I now have a greater understanding
of
PART of my problem - my SQLDirectory is not *quite* right, I think. So
I'
Sorry to reply to my own post, but I now have a greater understanding of
PART of my problem - my SQLDirectory is not *quite* right, I think. So I'm
rolling back to FSDirectory.
Now, I have a servlet that writes to the filesystem to simplify things (as
I'm not confident enough to debug the RDMS-bas
Gus Kormeier wrote:
Not sure if our installation is the same or not, but we are also using
Tomcat.
I had a similiar problem last week, it occurred after Tomcat went through a
hard restart and some software errors had the website hammered.
I found the lock file in /usr/local/tomcat/temp/ using loca
: 'Lock obtain timed out' even though NO locks exist...
James Dunn wrote:
>Which version of lucene are you using? In 1.2, I
>believe the lock file was located in the index
>directory itself. In 1.3, it's in your system's tmp
>folder.
>
>
Yes... 1.3 and I hav
James Dunn wrote:
Which version of lucene are you using? In 1.2, I
believe the lock file was located in the index
directory itself. In 1.3, it's in your system's tmp
folder.
Yes... 1.3 and I have a script that removes the locks from both dirs...
This is only one process so it's just fine t
Kevin A. Burton wrote:
Actually this is exactly the problem... I ran some single index tests
and a single process seems to read from it.
The problem is that we were running under Tomcat with diff webapps for
testing and didn't run into this problem before. We had an 11G index
that just took a
[EMAIL PROTECTED] wrote:
It is possible that a previous operation on the index left the lock open.
Leaving the IndexWriter or Reader open without closing them ( in a finally
block ) could cause this.
Actually this is exactly the problem... I ran some single index tests
and a single process see
Which version of lucene are you using? In 1.2, I
believe the lock file was located in the index
directory itself. In 1.3, it's in your system's tmp
folder.
Perhaps it's a permission problem on either one of
those folders. Maybe your process doesn't have write
access to the correct folder and
It is possible that a previous operation on the index left the lock open.
Leaving the IndexWriter or Reader open without closing them ( in a finally
block ) could cause this.
Anand
-Original Message-
From: Kevin A. Burton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 28, 2004 2:57 PM
> -Original Message-
> From: Tatu Saloranta [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 16, 2003 7:23 AM
> To: Lucene Users List
> Subject: Re: Lock obtain timed out
>
> On Tuesday 16 December 2003 03:37, Hohwiller, Joerg wrote:
> > Hi there,
>
On Tuesday 16 December 2003 03:37, Hohwiller, Joerg wrote:
> Hi there,
>
> I have not yet got any response about my problem.
>
> While debugging into the depth of lucene (really hard to read deep insde) I
> discovered that it is possible to disable the Locks using a System
> property.
...
> Am I sa
Hi there,
thanks for your resonse guys!
For the answers I got the info that I must not have an IndexWriter
and an IndexReader open at the same time that both want to modify
the index - even sequentially.
What I have is the following:
1 Thread is working out events such as resource (file or fold
close it at anytime?
David
-Original Message-
From: Morus Walter [mailto:[EMAIL PROTECTED]
Sent: 16 December 2003 11:08
To: Lucene Users List
Subject: Re: Lock obtain timed out
Hohwiller, Joerg writes:
>
> Am I safe disabling the locking???
No.
> Can anybody tell m
Hohwiller, Joerg writes:
>
> Am I safe disabling the locking???
No.
> Can anybody tell me where to get documentation about the Locking
> strategy (I still would like to know why I have that problem) ???
>
I guess -- but given your input I really have to guess; the source you
wanted to attach di
Hi.
I obtained this exception when I had more than one thread trying to create
an IndexWriter.
I solved it by placing the code using the IndexWriter in a synchronized
method.
Hope it will help,
Gilles.
-Message d'origine-
De : Hohwiller, Joerg [mailto:[EMAIL PROTECTED]
Envoyé : mardi 16
18 matches
Mail list logo
