David Spencer wrote:
JiÅÃ Kuhn wrote:
This doesn't work either!
You're right.
I'm running under JDK1.5 and trying larger values for -Xmx and it
still fails.
Running under (Borlands) OptimzeIt shows the number of Terms and
Terminfos (both in org.apache.lucene.index) increase every time thru
the
code should run endlesly (I have said it before: in version 1.4 final
it does).
Jiri.
-Original Message-
From: David Spencer [mailto:[EMAIL PROTECTED]
Sent: Monday, September 13, 2004 5:34 PM
To: Lucene Users List
Subject: force gc idiom - Re: OutOfMemory example
JiÅÃ Kuhn wrote:
Thanks f
ersion 1.4 final
it does).
Jiri.
-Original Message-
From: David Spencer [mailto:[EMAIL PROTECTED]
Sent: Monday, September 13, 2004 5:34 PM
To: Lucene Users List
Subject: force gc idiom - Re: OutOfMemory example
JiÅÃ Kuhn wrote:
Thanks for the bug's id, it seems like my problem and I
said it before: in version 1.4 final it does).
Jiri.
-Original Message-
From: David Spencer [mailto:[EMAIL PROTECTED]
Sent: Monday, September 13, 2004 5:34 PM
To: Lucene Users List
Subject: force gc idiom - Re: OutOfMemory example
JiÅÃ Kuhn wrote:
Thanks for the bug's id, it see
ion of my code. I believe that the code should
run endlesly (I have said it before: in version 1.4 final it does).
Jiri.
-Original Message-
From: David Spencer [mailto:[EMAIL PROTECTED]
Sent: Monday, September 13, 2004 5:34 PM
To: Lucene Users List
Subject: force gc idiom - Re: OutOfMemor
34 PM
To: Lucene Users List
Subject: force gc idiom - Re: OutOfMemory example
JiÅÃ Kuhn wrote:
> Thanks for the bug's id, it seems like my problem and I have a stand-alone code with
> main().
>
> What about slow garbage collector? This looks for me as wrong suggestion.
I
JiÅÃ Kuhn wrote:
Thanks for the bug's id, it seems like my problem and I have a stand-alone code with
main().
What about slow garbage collector? This looks for me as wrong suggestion.
I've seen this written up before (javaworld?) as a way to probably
"force" GC instead of just a System.gc() call