Return-Path: Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 13303 invoked from network); 30 Sep 2003 15:17:00 -0000 Received: from unknown (HELO warhawk.mpi.com) (63.244.250.133) by daedalus.apache.org with SMTP; 30 Sep 2003 15:17:00 -0000 Received: from lightning.mpi.com (lightning.mpi.com [63.244.252.11]) by warhawk.mpi.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h8UFFMF05741 for ; Tue, 30 Sep 2003 11:15:22 -0400 (EDT) Received: from US-VS1.corp.mpi.com (us-be2.corp.mpi.com [63.244.252.32]) by lightning.mpi.com (Switch-3.0.5/Switch-3.0.0) with ESMTP id h8UFGxpH012358 for ; Tue, 30 Sep 2003 11:17:00 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Signal 11 Error: An unexpected exception in native code outside the VM Date: Tue, 30 Sep 2003 11:09:47 -0400 Message-ID: <9C5166762F311146951505C6790A9CF8013DF3B9@US-VS1.corp.mpi.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Signal 11 Error: An unexpected exception in native code outside the VM Thread-Index: AcOHZHF2BQu4i5iqT8Oo3M2gw9DQ8wAAA5iQ From: "Shapira, Yoav" To: "Tomcat Users List" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Howdy, >Right now the server has all of the latest and >greatest patches from Red Hat. We are still seeing >crashes about once a day. OK, so we can rule out OS patches as the cause ;) >I am also observing a significant memory leak on this >box, though I can't figure out if its Tomcat, java, >the code or something else - once the memory gets low >enough tomcat crashes. Once the memory gets low enough, the server will crash, yes. It's likely that if you find and fix the memory leak, your crashing problem will go away. >I am planning on making the following config changes >to hopefully remedy this problem: > >-Xms512m -Xmx512m -XX:NewSize=3D256m -XX:MaxNewSize=3D512m >-Xincgc Doesn't make sense at all. The new generation size should never be the entire heap, as that leaves no room for long-lived objects and will have your JVM thrashing all the time. If your machine has 2GB of memory, maybe something like -Xmx1024m -XX:MaxNewSize=3D256m is more reasonable. Experiment with incremental collection (-Xincgc) but don't expect it to be a miracle cure. Finally, if your memory leak is serious enough, your garbage collections settings may not help at all. Use a profiler to determine where and why the memory leak is happening, and fix it in the code. Yoav Shapira This e-mail, including any attachments, is a confidential business com= munication, and may contain information that is confidential, propriet= ary and/or privileged. This e-mail is intended only for the individua= l(s) to whom it is addressed, and may not be saved, copied, printed, d= isclosed or used by anyone else. If you are not the(an) intended reci= pient, please immediately delete this e-mail from your computer system= and notify the sender. Thank you.