Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01CA406B.3CF159CE"
Subject: Memory issues with jackrabbit/lucene
Date: Mon, 28 Sep 2009 14:41:04 -0400
Message-ID: 
 <8A3DD82403361A4890D736E1CC87D77D7F869D@WINDGATE.ds.searchspace.com>
Thread-Topic: Memory issues with jackrabbit/lucene
Thread-Index: Aco92yTZELJbM18SSpWVnTkZIPeuiwCkAGFQ
From: "Muguet Bradbury" <M.Bradbury@fortent.com>
To: <users@jackrabbit.apache.org>

------_=_NextPart_001_01CA406B.3CF159CE
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Repeating this question since I have not received any responses.  Does
anyone have any ideas on this problem?

=20

________________________________

From: Muguet Bradbury=20
Sent: Friday, September 25, 2009 8:25 AM
To: users@jackrabbit.apache.org
Subject: Memory issues with jackrabbit/lucene

=20

We are experiencing memory leaks in our application that uses jackrabbit
1.4.  When we analyze the heap dump, there are many instances of Lucene
TermBuffer objects in the heap when the exception occurs.  Upon
inspection of the TermBuffer objects, we see document content that we
want to store, but we don't want to be able to search within this
content.

=20

Is there a way to add content to a jackrabbit repo without making it
searchable, thus avoiding the TermBuffer objects being created? =20

=20

Thanks!

Muguet Bradbury


------_=_NextPart_001_01CA406B.3CF159CE--