Dear Todd,
I'm not sure I can use session counting, as my
session size is not consistent. I could try to estimate
the size of each session, and keep a global counter,
but that seems like a lot of work.
JMX offers quite a bit of insight in what your GC is doing. You could
implement throttling as a function of the number of full GC's that
your system experiences. While full GC's do happen from time to time,
you could trigger if they happen more than once per so-many seconds.
Actual values would probably be highly application-specific.
I agree with someone else that 256MB is not a whole lot or RAM for a
busy server. With current prices of RAM I would go for a gig or two
and take it from there.
I understand that garbage collection is, err, whimsical,
but I think I'm going to give it a go anyway.
I will keep in mind that the memory results
from Runtime will probably under-report the
available memory. I'm going to add an explicit
request for garbage collection, _before_ the memory
becomes seriously depleted.
Here is what happens if you do http://java-monitor.com/forum/showthread.php?t=188
It is not pretty, I can tell you that. I add -XX:-DisableExplicitGC
to my JAVA_OPTS for this very reason.
--
Kees Jan
http://java-monitor.com/forum/
kjkos...@kjkoster.org
06-51838192
The secret of success lies in the stability of the goal. -- Benjamin
Disraeli
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
