Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 64331 invoked from network); 20 Dec 2004 22:43:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 20 Dec 2004 22:43:15 -0000 Received: (qmail 41821 invoked by uid 500); 20 Dec 2004 22:41:09 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 41799 invoked by uid 500); 20 Dec 2004 22:41:08 -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 41775 invoked by uid 99); 20 Dec 2004 22:41:08 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of pc.greenus@gmail.com designates 64.233.184.205 as permitted sender) Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.205) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 20 Dec 2004 14:41:05 -0800 Received: by wproxy.gmail.com with SMTP id 55so37264wri for ; Mon, 20 Dec 2004 14:41:00 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=P1eiAmOphXabRsPP4c758apIg6dUukwjNTVRwgZL1QkUfWKozxlppN4eQv/gMxeF6sUqb1qrjmLuL6QIhYL0YvNhtgKSyPbSyy624r7iQ4EM7+tLrJ6e+VvLeEa/GXKvaHOR2j/DBRAeo6mTTHHwYdPjlkJGiybWIJuOr6PPHPQ= Received: by 10.54.28.65 with SMTP id b65mr400723wrb; Mon, 20 Dec 2004 14:41:00 -0800 (PST) Received: by 10.54.27.10 with HTTP; Mon, 20 Dec 2004 14:41:00 -0800 (PST) Message-ID: <45b72a5704122014417d3fd94e@mail.gmail.com> Date: Mon, 20 Dec 2004 22:41:00 +0000 From: Eric Rotick Reply-To: Eric Rotick To: Tomcat Users List Subject: Re: Tomcat/JVM crashes on Linux In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <88FE95E1-52B0-11D9-ADC4-000A95DA5A64@lapcominc.com> <41C719E8.7030002@redesetgrow.com> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N The application receives data packets from acoustic sensors. While the total load is not huge, because of the way the data is collected there are periods of no activity and then periods when all hell breaks loose. This happens every 15 minutes and we size the memory based on the use of swap over a 24 hour period. Tomcat is by far this biggest process and it can grow quite large due to internal queuing waiting for other services to become available. On average there are 2,500 hits every 15 minutes spread across 2 machines in a cluster. On Mon, 20 Dec 2004 15:15:17 -0500, Greg Lappen wrote: > What kind of load does your application handle? I am not processing a > HUGE amount of requests, but we server about 6000 visitors a day, > 15,000 pages. > > Greg > On Dec 20, 2004, at 1:28 PM, Wade Chandler wrote: > > > Greg Lappen wrote: > >> Hello- > >> Has anyone had a problem with Tomcat 5.0.28 crashing on Linux with no > >> error messages? > >> My production server running with JDK 1.4.2_06, RedHat EL 3.0 just > >> crashes, no core dump, no errors in catalina.out, no clues. > >> Sometimes it goes for days, sometimes it happens several times in one > >> day. I am running the tomcat process behind Apache 2 with mod_proxy. > >> Setting "ulimit -c unlimited" in the catalina.sh startup file still > >> did not produce a core file. > >> If nobody else has experienced this, do you have any suggestions on > >> how to debug it further? > >> Thanks, > >> Greg > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org > >> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org > > > > I'm using the same setup as you less Apache2. I use tomcat as the web > > server. Using TC5.0.28 and JDK1.4.2_06, and I have yet to have the > > server crash once. Not much help, but might give you some clues where > > to look. > > > > Connector log (mod_proxy....assuming you mean you're using the new > > connector code)....is there anything in the Apache2 log? I assume > > from your post you mean that the java process just completely goes > > away. You might find (depending on the running directory of the java > > process running tomcat) a pid dump log file or something...not sure if > > the vm produces one of these or not. You also might check in > > /var/log/messages file to see if for some reason the kernel or some > > lib got some error it logged. > > > > Wade > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org > > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org