-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Konstantin,
On 8/12/2010 7:48 AM, Konstantin Kolinko wrote: > It looks that with your version of JRE and with your setting it is > better to run with gcDaemonProtection="false". I certainly do not > know how other JRE versions behave here. (Feedback is welcomed). That's what he's got, now: gcDaemonProtection="false" (see the OP), but the GC is still happening. Donald, the reason the JreMemoryLeakPreventionListener makes the call to GC.requestLatency is to un-do the effect of some other component (RMI, it seems). It's possible that some component other than the JreMemoryLeakPreventionListener is causing the periodic full GC. Try disabling the listener altogether and see if the GCs go away. If they don't, consider recompiling the JreMemoryLeakPreventionListener with some debugging code in there (the current code does not emit any logging unless there is a problem calling GC.requestLatency... it does not announce it's intention of doing so, even at a TRACE level). - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxkAfAACgkQ9CaO5/Lv0PBgjACgkeQyW4H949HJ/k+28hjKR3JH 9tsAoLIxzWfypWAhR9PzC4IQpGFF0Kwy =5GDP -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
