Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Message-ID: <464A4952.7060407@anu.edu.au>
Date: Wed, 16 May 2007 09:59:14 +1000
From: Stephen Gray <Stephen.Gray@anu.edu.au>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: java-user@lucene.apache.org
Subject: Re: Memory leak (JVM 1.6 only)
References: <464953A9.5030004@anu.edu.au> <46499B50.9060307@gmail.com>
In-Reply-To: <46499B50.9060307@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Thanks, that narrows it down a bit.

Thanks for all the replies to my question.

Steve

Mark Miller wrote:
> I don't have much help to offer other than to say I am also using a 
> tweaked version of the IndexAccess code you are, with java 1.6, with 
> hundreds of thousands to millions of docs, at multiple locations, for 
> months -- and I have not seen any memory leaks. Leads me to think the 
> leak may be with your code and not any Lucene code...
>
> I will mention that the IndexAccess code does not handle 
> multi-searchers very well without some adjustments, but even that 
> should not cause a leak.
>
> Keep playing with the Netbeans profiler...if it really is a leak, you 
> aught to be able to find it.
>
> - Mark
>
> Stephen Gray wrote:
>> Hi everyone,
>>
>> I have an application that indexes/searches xml documents using 
>> Lucene. I'm having a problem with what looks like a memory leak, 
>> which occurs when indexing a large number of documents, but only when 
>> the application is running under JVM 1.6. Under JVM 1.5 there is no 
>> problem. What happens is that the memory allocated consistently rises 
>> during indexing until the JVM crashes with an OutOfMemory exception.
>>
>> I'm using Lucene 2.1, and am using Maik Schreiber's LuceneIndexAccess 
>> API, which hands out references to cached 
>> IndexWriter/Reader/Searchers to objects that need to use them, and 
>> handles closing and re-opening IndexSearchers after documents are 
>> added to the index. The application is running under Tomcat 6.
>>
>> I'm a bit out of my depth determining the source of the leak - I've 
>> tried using Netbeans profiler, which shows a large number of HashMap 
>> instances that survive a long time, but these are created by many 
>> different classes so it's difficult to pinpoint one source.
>>
>> Has anyone found similar problems with Lucene indexing operations 
>> running under JVM 1.6? Does anyone have any suggestions re how to 
>> deal with this?
>>
>> Any help much appreciated.
>>
>> Thanks,
>> Steve
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: java-user-help@lucene.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>


-- 
Stephen Gray
Archive IT Officer
Australian Social Science Data Archive
18 Balmain Crescent (Building #66)
The Australian National University
Canberra ACT 0200

Phone +61 2 6125 2185
Fax +61 2 6125 0627
Web http://assda.anu.edu.au/

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