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 5E0CDF1BB for ; Tue, 2 Apr 2013 08:51:02 +0000 (UTC) Received: (qmail 71937 invoked by uid 500); 2 Apr 2013 08:50:59 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 70780 invoked by uid 500); 2 Apr 2013 08:50:58 -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 70736 invoked by uid 99); 2 Apr 2013 08:50:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Apr 2013 08:50:57 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of aw@ice-sa.com designates 212.85.38.228 as permitted sender) Received: from [212.85.38.228] (HELO tor.combios.es) (212.85.38.228) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Apr 2013 08:50:49 +0000 Received: from [192.168.245.129] (p549E8E33.dip0.t-ipconnect.de [84.158.142.51]) (Authenticated sender: andre.warnier@ice-sa.com) by tor.combios.es (Postfix) with ESMTPA id 304DF3C06FB for ; Tue, 2 Apr 2013 10:50:54 +0200 (CEST) Message-ID: <515A9BD6.20706@ice-sa.com> Date: Tue, 02 Apr 2013 10:50:30 +0200 From: =?ISO-8859-1?Q?Andr=E9_Warnier?= Reply-To: Tomcat Users List User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Re : Memory leak in Tomcat 6.0.35 ( 64 bit) References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org saumil shah wrote: > Hello there, > > I recently deployed one of the COTS products SAP Business Objects. When the product was deployed , everything seemed to run fine but yesterday we started experiencing "Service is unavailable" error , upon enabling DEBUG logs in Tomcat , we saw the error below with memory leak message. We were wondering what could have caused it .... > The Tomcat is 64 bit (huh ?) , JVM is 64 bit but the applications deployed are 32 bit webapps (huh ?) .... we say Tomcat6 process becoming unresponsive around 2GB mark. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org