List"
Subject: Re: JreMemoryLeakPreventionListener and hourly Full GC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donald,
On 8/12/2010 5:04 PM, Donald Armstrong wrote:
> 3) className="org.apache.catalina.core.JreMemoryLeakPreventionListener"
> gcDaemonProtection="false
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donald,
On 8/12/2010 5:04 PM, Donald Armstrong wrote:
> 3) className="org.apache.catalina.core.JreMemoryLeakPreventionListener"
> gcDaemonProtection="false"/>
[snip]
> We've decided to go with option 3.
I'm confused... I thought you tried that and
Thank you Konstantin and Chris for your attention.
As stated in the initial post:
'We have recently deployed tomcat-6.0.28 in our organization and are
noticing every hour, a Full GC is occurring. The same application,
same JVM, same JVM args, just a new tomcat release.'
Using the default JreMemo
-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
2010/8/12 Donald Armstrong :
> The documentation does not indicate if the
> JreMemoryLeakPreventionListener should be enabled for production
> environments, but based on this information, probably not?
>
I think you are too fast jumping to conclusions.
BTW, even if you do not see JavaDoc here
htt
Thanks for your attention chris,
We've identified why every hour: sun.misc.GC.requestLatency(360l)
I was able to confirm with the tomcat documentation that with
gcDaemonProtection enabled, the "GC Daemon" thread is running.
We've identified why the Full GC; I've looked at the decompiled cod
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donald,
On 8/11/2010 12:15 PM, Donald Armstrong wrote:
> We have recently deployed tomcat-6.0.28 in our organization and are
> noticing every hour, a Full GC is occurring. The same application,
> same JVM, same JVM args, just a new tomcat release.
>
Hello,
We have recently deployed tomcat-6.0.28 in our organization and are
noticing every hour, a Full GC is occurring. The same application,
same JVM, same JVM args, just a new tomcat release.
I have addressed the issue by adjusting the server.xml and disabling
gcDaemonProtection.
Ideas on w
