Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 95508 invoked from network); 2 Aug 2002 17:29:07 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 2 Aug 2002 17:29:07 -0000 Received: (qmail 7711 invoked by uid 97); 2 Aug 2002 17:29:08 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 7695 invoked by uid 97); 2 Aug 2002 17:29:07 -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 7683 invoked by uid 98); 2 Aug 2002 17:29:07 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <3D4AC144.4030800@joedog.org> Date: Fri, 02 Aug 2002 13:28:36 -0400 From: Tim Funk Organization: Human being User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Apache + Tomcat sometimes pegs CPU References: <00e501c23a46$737b7e30$6c01a8c0@qec.com> <00f101c23a46$d81d5d40$6c01a8c0@qec.com> 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: daedalus.apache.org 1.6.2 0/1000/N Upgrade to 4.0.4. Earlier (4.0.X) versions have a problems with POST requests when the browser terminates before sending enough data. This caused an infinite loop between apache and tomcat. Here is the simple way to reproduce, (and watch your cpu go way up): ------------------------------------ % telnet webserver 80 POST /somepage.jsp HTTP/1.1 Host: webserver:80 Connection: Close Content-Type: application/x-www-form-urlencoded Content-Length: 200 PutStuff here and kill telnet session before 200 chars ------------------------------------ -Tim Jeff Larsen wrote: > I forgot to mention... Even when the CPU is pegged, > the site functions normally. > > Jeff > > ----- Original Message ----- > From: "Jeff Larsen" > To: "tomcat-user" > Sent: Friday, August 02, 2002 12:02 PM > Subject: Apache + Tomcat sometimes pegs CPU > > > >>I'm running Apache 1.3.23/Tomcat 4.0.3 (jdk1.3.1) >>on Solaris 7 connected with mod_jk. Sometimes I >>I find that the CPU on the web server box is pegged >>at 100%. It's a dedicated server and I am bouncing >>Apache and Tomcat once a week to help alleviate the >>problem. If I didn't restart every week, it would just >>be a matter of time before things spiraled out of >>control again. >> >>The processes that are responsible are java (Tomcat) >>and libhttpd.ep (Apache, with --enable-rule=SHARED_CORE) >>each with about 50% of the CPU. >> >>If I bounce Tomcat, no change. If I bounce Apache, >>it returns to normal (low) CPU usage. I have Apache >>running on other machines without Tomcat and this >>does not happen. >> >>So it's got to be a mod_jk thing. There are no log >>messages of any significance. Any ideas on how to >>fix it? >> >>Thanks, >> >>Jeff >> >> >> >>-- >>To unsubscribe, e-mail: > > > >>For additional commands, e-mail: > > > > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > > -- To unsubscribe, e-mail: For additional commands, e-mail: