Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <44F816E4.1070705@mikemccandless.com>
Date: Fri, 01 Sep 2006 07:17:56 -0400
From: Michael McCandless <lucene@mikemccandless.com>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: java-user@lucene.apache.org
Subject: Re: Lock error attempting update of RAMDirectory index
References: <6089447.post@talk.nabble.com>
	 <1157066620.4727.3.camel@localhost>  <6091907.post@talk.nabble.com>
 <1157107579.4727.10.camel@localhost>
In-Reply-To: <1157107579.4727.10.camel@localhost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

>>> You probably forgot to close an IndexWriter?
>> Well, I wish it were that easy...I open one IndexWriter to write the
>> documents to the index after it is created, and then call writer.optimize()
>> and writer.close().  Your suggestion is a good one in that, from what I've
>> read, the writer needs to be closed to release the lock file.  Apparently,
>> there is more to it than that.  Also, this doesn't happen consistently --
>> just occasionally.
> 
> Set a breakpoint, print the stacktrace of a new instance of Exception to
> your log, or do something similar in the lock methods of Lucene so you
> will find out what code of yours lock and unlocks the index. 
> 
> I'm quite convinced you forget to close something. Or perhaps you try to
> modify at the same time as you insert documents.

Why do you need an IndexWriter at all?  Can't you open a single 
IndexModifier and use to do all adds/deletes against your RAMDirectory? 
  Or maybe I'm not understanding the full context...

Mike

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org