Thanks, the link was helpful. I'll let you know if I find anything.
Thanks for all the replies to this.
Steve
Doron Cohen wrote:
Stephen Gray wrote:
Thanks. If the extra memory allocated is native memory I don't think
jconsole includes it in "non-heap" as it doesn't show this as
increasin
Stephen Gray wrote:
> Thanks. If the extra memory allocated is native memory I don't think
> jconsole includes it in "non-heap" as it doesn't show this as
> increasing, and jmap/jhat just dump/analyse the heap. Do you know of an
> application that can report native memory usage?
Sorry, but I didn
I actually had to deal with a leak in non-heap native memory once. I am
running on Linux so I just use good old "ps" to monitor native memory usage.
Bill
On 5/18/07, Stephen Gray <[EMAIL PROTECTED]> wrote:
Thanks. If the extra memory allocated is native memory I don't think
jconsole includes
Thanks. If the extra memory allocated is native memory I don't think
jconsole includes it in "non-heap" as it doesn't show this as
increasing, and jmap/jhat just dump/analyse the heap. Do you know of an
application that can report native memory usage?
Thanks,
Steve
Doron Cohen wrote:
Stephen
Stephen Gray <[EMAIL PROTECTED]> wrote on 17/05/2007 22:40:01:
> One interesting thing is that although the memory allocated as
> reported by the processes tab of Windows Task Manager goes up and up,
> and the JVM eventually crashes with an OutOfMemory error, the total size
> of heap + non-heap as
Hi Otis,
Thanks very much for your reply.
I've removed the LuceneIndexAccessor code, and still have the same
problem, so that at least rules out LuceneIndexAccessor as the source.
maxBufferedDocs is just set to the default, which I believe is 10.
I've tried jconsole, + jmap/jhat for looking
Hi Steve,
You said the OOM happens only when you are indexing. You don't need
LuceneIndexAccess for that, so get rid of that to avoid one suspect that is not
part of Lucene core. What is your maxBufferedDocs set to? And since you are
using JVM 1.6, check out jmap, jconsole & friends, they'll
Daniel Noll wrote:
On Tuesday 15 May 2007 21:59:31 Narednra Singh Panwar wrote:
try using -Xmx option with your Application. and specify maximum/ minimum
memory for your Application.
It's funny how a lot of people instantly suggest this. What if it isn't
possible? There was a situation a wh
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 multip
On Tuesday 15 May 2007 21:59:31 Narednra Singh Panwar wrote:
> try using -Xmx option with your Application. and specify maximum/ minimum
> memory for your Application.
It's funny how a lot of people instantly suggest this. What if it isn't
possible? There was a situation a while back where I sa
try using -Xmx option with your Application. and specify maximum/ minimum
memory for your Application.
Hope this will solve you problem.
On 5/15/07, Stephen Gray <[EMAIL PROTECTED]> wrote:
Hi everyone,
I have an application that indexes/searches xml documents using Lucene.
I'm having a prob
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 y
12 matches
Mail list logo
