Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 22606 invoked from network); 25 Sep 2007 15:29:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Sep 2007 15:29:04 -0000 Received: (qmail 80399 invoked by uid 500); 25 Sep 2007 15:28:42 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 80378 invoked by uid 500); 25 Sep 2007 15:28:42 -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 80367 invoked by uid 99); 25 Sep 2007 15:28:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Sep 2007 08:28:42 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of aoeshang@gmail.com designates 64.233.184.230 as permitted sender) Received: from [64.233.184.230] (HELO wr-out-0506.google.com) (64.233.184.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Sep 2007 15:28:42 +0000 Received: by wr-out-0506.google.com with SMTP id c48so664190wra for ; Tue, 25 Sep 2007 08:28:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=+5dUX8U4LbJhWzk3fPQ38z737yB05sR84LpEq8+14Qc=; b=UBVgZwI59zfRgGCCBLNTP3Co+TnT9h3VbyPIOVrLLzS70+HKwThjWVClNE8ZF6PtZR7oq0eoodAMhkRh6Bs1OOZhkGG1F61Q+q8UscvBlEgILoz2xS7lhw8+yowAu5Ytcl/YjoZsfyH314XLRQGdxqvFNmIC8hjf73jHRA5KQjw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=WEDtkQlUryooSXSBbSrT7hRSsP5XO9kQflaMtbpXoxg/TonxT50K3yInjmnmsncQOsQbZtC+JkLjfATyTPy1bnjlQMwwuDtNaKBM7kE3dpnvVyx/bDAzaUKziLeUabmYwgdly/BhAhMggHBzQ3ifxkdOfhTH4W1zAREExz+C2Jg= Received: by 10.142.240.9 with SMTP id n9mr1841164wfh.1190734099321; Tue, 25 Sep 2007 08:28:19 -0700 (PDT) Received: by 10.70.63.13 with HTTP; Tue, 25 Sep 2007 08:28:19 -0700 (PDT) Message-ID: Date: Tue, 25 Sep 2007 11:28:19 -0400 From: "Jiansen Niu" To: "Tomcat Users List" Subject: Re: tomcat5.1 out of memory for swap space not released! In-Reply-To: <12873626.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_3352_14167231.1190734099271" References: <46F89DDF.8000903@apache.org> <12873626.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_3352_14167231.1190734099271 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I have been using Tomcat 6.0 since it was released and I would say that it is much better that Tomcat 5.x. As addressed in its release document, besides support Servlet 2.5 and JSP2.1, Tomcat 6.0 made following improvements upon Tomcat 5.5: - Memory usage optimizations - Advanced IO capabilities - Refactored clustering Not sure whether you turned on Security Manager for you Tomcat 5.0, as I know there is a memory leak related defect for Tomcat 5.0 when Security Manager is turned on and has been fixed since Tomcat 5.5.3 (Tomcat 6.0 has it fixed too). There are other memory leaks related defects that have been fixed since Tomcat 5.0, please refer to bug report for more details. Make sure you have a up to date JDK when you using Tomcat 6.0 since there are some NIO send file related bugs in this release for Linux based systems, or you can disable send file behavior in the Connector if you JDK is not up to date. Jiansen Niu On 9/25/07, JacquiYan wrote: > > > Dear Mark: > How about Tomcat 6.0?The lastest version is 6.0.Had the memory leaks been > fixed in Tomcat6.0?And further more,is tomcat6.0 a standy version? > > > > Mark Thomas-15 wrote: > > > > Tomcat 5.0.x has some memory leaks but as far as I recall they were > > mostly related to context reload. > > > > If you are reloading your app, I'd suggst an upgrade to the latest > > 5.5.x. If you are not reloading, then your app probably has a memory > > leak. I'd suggest using a profiler such as YourKit to try and track it > > down. > > > > Mark > > > > --------------------------------------------------------------------- > > To start a new topic, e-mail: users@tomcat.apache.org > > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org > > For additional commands, e-mail: users-help@tomcat.apache.org > > > > > > > > -- > View this message in context: > http://www.nabble.com/tomcat5.1-out-of-memory-for-swap-space-not-released%21-tf4513476.html#a12873626 > Sent from the Tomcat - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org > For additional commands, e-mail: users-help@tomcat.apache.org > > ------=_Part_3352_14167231.1190734099271--