Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 93363 invoked from network); 2 Dec 2003 17:52:19 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 2 Dec 2003 17:52:19 -0000 Received: (qmail 83411 invoked by uid 500); 2 Dec 2003 17:50:03 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 83352 invoked by uid 500); 2 Dec 2003 17:50:03 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 83261 invoked from network); 2 Dec 2003 17:50:02 -0000 Received: from unknown (HELO rwcrmhc11.comcast.net) (204.127.198.35) by daedalus.apache.org with SMTP; 2 Dec 2003 17:50:02 -0000 Received: from comcast.net (pcp725580pcs.arlngt01.va.comcast.net[68.49.187.119]) by comcast.net (rwcrmhc11) with SMTP id <2003120217500501300dru9te> (Authid: christopher.d.schultz); Tue, 2 Dec 2003 17:50:05 +0000 Message-ID: <3FCCD2BB.1040806@comcast.net> Date: Tue, 02 Dec 2003 12:58:19 -0500 From: Christopher Schultz User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomcat Users List Subject: Re: OutOfMemory Exception initializing page context References: <004001c3b8fb$42ea4fa0$7c1410ac@support1> In-Reply-To: <004001c3b8fb$42ea4fa0$7c1410ac@support1> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Rob, > I consulted with the developers and they said we don't use or do > anything that you suggested except we do use tomcat's connection pooling > for oracle. Okay, that's good. Sometimes, people don't use connection pooling or do it improperly, and leave Connection objects lying around. SQL Connection objects do not clean themselves up nicely, if they even clean themselves up... > We are running Sun j2sdk1.4.2_02 with the Concurrent Mark > Sweep GC with -Xmx512m. I currently use the verbose logging for GC > times. The odd thing is that it does not seem to progressively go up > but rather spike up with high GC times and the full GC will not clean > anything out. Hmm... that's a little odd. You say you get huge, sudden spikes from which the GC cannot recover? That sounds like bad news. Do you have any data on which pieces of code (servlets, JSPs, actions) are being executed when this happens? Consider adding a request logger filter to see what might be causing the spike... -chris --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org