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 041EA9D76 for ; Mon, 30 Jan 2012 16:24:39 +0000 (UTC) Received: (qmail 7340 invoked by uid 500); 30 Jan 2012 16:24:35 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 7255 invoked by uid 500); 30 Jan 2012 16:24:34 -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 7240 invoked by uid 99); 30 Jan 2012 16:24:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jan 2012 16:24:34 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dckerber@verizon.net designates 206.46.173.19 as permitted sender) Received: from [206.46.173.19] (HELO vms173019pub.verizon.net) (206.46.173.19) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jan 2012 16:24:26 +0000 Received: from [172.17.47.42] ([unknown] [64.17.225.82]) by vms173019.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LYM00I5GDJPMQO0@vms173019.mailsrvcs.net> for users@tomcat.apache.org; Mon, 30 Jan 2012 10:23:55 -0600 (CST) Message-id: <4F26C41A.8080304@verizon.net> Date: Mon, 30 Jan 2012 11:23:54 -0500 From: David kerber User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11 MIME-version: 1.0 To: Tomcat Users List Subject: Re: Java.lang.out.of.memory not clearly.... References: <4F22DCF1.7030208@pidster.com> <4F22EDB9.9020404@pidster.com> <4F230BE8.1010501@pidster.com> <7215BA462D00D343B2837F9113F0131F010574F905@POSTOFFICE02.polydyne.com> <7215BA462D00D343B2837F9113F0131F010574F953@POSTOFFICE02.polydyne.com> <99C8B2929B39C24493377AC7A121E21FB010D92A01@USEA-EXCH8.na.uis.unisys.com> 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 On 1/30/2012 11:05 AM, Luciano Andress Martini wrote: > 2012/1/30, Caldarale, Charles R: >>> From: Luciano Andress Martini [mailto:777user@gmail.com] >>> Subject: Re: Java.lang.out.of.memory not clearly.... >> >>> Jeffrey im sorry, but i need to ask, my boss says that is impossible >>> to be a problem in the software cause java unalocate objects >>> automatically, is that true? >> >> A) Stop your top posting - it's incredibly annoying and makes people much >> less likely to help. >> >> B) Your boss is wrong. Google for many examples of memory leaks in Java. >> >> - Chuck >> >> >> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY >> MATERIAL and is thus for use only by the intended recipient. If you received >> this in error, please contact the sender and delete the e-mail and its >> attachments from all computers. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org >> For additional commands, e-mail: users-help@tomcat.apache.org >> >> > > Thank you and sorry Chuck. > Jeffrey what is your opinion about this? > The development team is using a software that "Draw" java code called > developer, and do not programming in. Im a assembler/C programmer and > don't have so much knowing about java. Java can have memory leaks just as easily as C can, but if the app is standalone, it will release them when the app closes and the JRE shuts down. I have killed tomcat more than once with memory leaks, so it's easy to do. I'm not the expert that Chuck and Mark T are, but here is my understanding of what happens: if the app is running under tomcat, the JRE never shuts down since tomcat is using it. That means the JRE can not free up memory that your app has left allocated, as it would be able to in a standalone app. So your Tomcat app has to clean up after itself because there is nothing else that can do so. > > But all the fault is falling back to me in the company. I know the feeling :-/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org