Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 73C4610566 for ; Wed, 11 Dec 2013 19:37:09 +0000 (UTC) Received: (qmail 89681 invoked by uid 500); 11 Dec 2013 19:37:06 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 89618 invoked by uid 500); 11 Dec 2013 19:37:05 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 89609 invoked by uid 99); 11 Dec 2013 19:37:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Dec 2013 19:37:05 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bharathchinnadurai@googlemail.com designates 74.125.82.54 as permitted sender) Received: from [74.125.82.54] (HELO mail-wg0-f54.google.com) (74.125.82.54) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Dec 2013 19:37:01 +0000 Received: by mail-wg0-f54.google.com with SMTP id n12so7046944wgh.9 for ; Wed, 11 Dec 2013 11:36:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=kB4lh++vbPRNSNNxUxncxqrFismEz2yLnpl+9vRPOww=; b=fsUI/7tDP8vNiAI5M9Sh7aH9f3yLoO6dMm2x3k5yF7uMszneIQYelCpx6W/kRXK3AN HHfQE4b217/XYWQls/bRbZc+e1Pey3yR3D3uxwfy8d7zvJq/5TYmwNxLpKkRVYY7iV3Q Vw+mr7iP0eH2l9ERReid8P/sYvATeQcc9KOvXi91l0E+FO9YT5wNEIVMdZfutmvTLU9J Yznh4A8RHdz63n+n8c6kIaPHKdJkjq/JU5TalNRG2Cy3JF25Yff6d2LN1v2r05E8t8/0 2NCU2ujg83bSLq8Ob2sZkpX/nVOYeNUl22auxvIGPIhLMcJ+moksFvMH2JYxW7wXye0M BVCA== MIME-Version: 1.0 X-Received: by 10.194.63.228 with SMTP id j4mr3115327wjs.34.1386790600293; Wed, 11 Dec 2013 11:36:40 -0800 (PST) Received: by 10.194.87.68 with HTTP; Wed, 11 Dec 2013 11:36:40 -0800 (PST) Date: Wed, 11 Dec 2013 14:36:40 -0500 Message-ID: Subject: Question on bug# 53267 in tomcat 7.0.47 From: bharath chinnadurai maharajan To: users@tomcat.apache.org Content-Type: multipart/alternative; boundary=047d7ba97f3a1bc3f604ed475906 X-Virus-Checked: Checked by ClamAV on apache.org --047d7ba97f3a1bc3f604ed475906 Content-Type: text/plain; charset=ISO-8859-1 Hello, This is my first post to the tomcat forum, so please excuse of any errors. I am looking at a fix for one of the bug (bug id#53267) in Catalina. Ref - https://issues.apache.org/bugzilla/show_bug.cgi?id=53267 The bug is in RESOLVED FIXED state. As per this bug, the one hr time interval (when a GC event is kicked off) was changed to Long.MAX ( a very long time). It is also mentioned the value is configurable using a system property - org.apache.catalina.core.jreMemoryLeakPreventionGCDaemonPeriod. When I tried setting this property to 3600000, assuming a full GC will be kicked every hour it did not happen. Curious, I looked into the code for version 7.0.47, that config variable was not used in org.apache.catalina.core.JreMemoryLeakPreventionListener. Code snippet from JreMemoryLeakPreventionListener in tomcat version 7.0.47 : Class clazz = Class.forName("sun.misc.GC"); Method method = clazz.getDeclaredMethod( "requestLatency", new Class[] {long.class}); method.invoke(null, Long.valueOf(Long.MAX_VALUE - 1)); Instead of using the Long.MAX_VALUE-1 by default, it should try and resolve if from the aforementioned system property. Am I wrong to assume the config variable will be present in 7.0.47? Thanks for your time, and my sincere apologies if I had wasted it. -- Bharath. --047d7ba97f3a1bc3f604ed475906--