CORRECTION:
Ok, I simplified my test case a little... I removed the UNC
share which is
a remote file share that Windows supports.
I have two processes
running
on the same Windows XP machine.
1) The first process uses an IndexWriter
to writes to the index and then closes the IndexWriter.
Ok, I simplified my test case a little... I removed the UNC share which is
a remote file share that Windows supports.
I have two processes running
on the same Windows XP machine.
1) The first process uses an IndexWriter
to writes to the index and then closes the IndexWriter.
2) The first pr
[EMAIL PROTECTED] writes:
> Hi Christoph,
>
> Thats what I thought. But what I'm seeing is this:
> - open
> reader for searching
> (the reader is opening an index on a remote machine
> (via UNC) which takes a couple seconds)
> - meanwhile the other service opens
> an IndexWriter and adds a docume
Hi Christoph,
Thats what I thought. But what I'm seeing is this:
- open
reader for searching
(the reader is opening an index on a remote machine
(via UNC) which takes a couple seconds)
- meanwhile the other service opens
an IndexWriter and adds a document
(the index writer determines that i
Morus Walter wrote:
AFAIK you should never open an IndexWriter and an IndexReader at the
same time. You should use only one of them at a time but you may open as
many IndexSearchers as you like for searching.
You cannot open an IndexSearcher without opening an IndexReader (explicitly
or implicitl
Christoph Kiehl writes:
>
> AFAIK you should never open an IndexWriter and an IndexReader at the
> same time. You should use only one of them at a time but you may open as
> many IndexSearchers as you like for searching.
>
You cannot open an IndexSearcher without opening an IndexReader (explici
[EMAIL PROTECTED] wrote:
I'm getting:
java.io.IOException: Lock obtain timed out
I have
a writer service that opens the index to delete and add docs. I have a reader
service that opens the index for searching only.
AFAIK you should never open an IndexWriter and an IndexReader at the
same time. Yo
Hi,
I'm getting:
java.io.IOException: Lock obtain timed out
I have
a writer service that opens the index to delete and add docs. I have a reader
service that opens the index for searching only.
This error occurs when
the reader service opens the index (this takes about 500ms). Meanwhile