We tried various memory configurations, running in the configuration you
suggested would(and did) cause an out of memory error in either of the two
cases. Thus the use of the word better, no args let java use as much memory
as available while not doing so limited it.
we used jdk1.4 (not sure exactly which version 01 would be my guess)
Jim
-----Original Message-----
From: Rouvet, Laurent [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 9:31 AM
To: 'Log4J Developers List'
Subject: RE: Large Memory usage while using log4j
> While this seems to be true in windows we do not get the same
behavior in
> Linux, in fact we get better memory usage if we omit the java memory
^^^^^^^^^^^^^^^^^^^^^
What that means, *better*?
> parameters in Linux. I agree this goes against the java documentation but
> this is what we experienced.
Which JDK version do you use?
Anyway, did you try with -Xmx100M
With this setting the GC will be less lazy... and you problem should be
fixed.
I hope this helps,
Laurent.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
