From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LjyVR-0001YL-DY for garchives@archives.gentoo.org; Wed, 18 Mar 2009 16:20:37 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C2CE9E0316; Wed, 18 Mar 2009 16:20:36 +0000 (UTC) Received: from mail-bw0-f172.google.com (mail-bw0-f172.google.com [209.85.218.172]) by pigeon.gentoo.org (Postfix) with ESMTP id 5C7C9E0316 for ; Wed, 18 Mar 2009 16:20:36 +0000 (UTC) Received: by bwz20 with SMTP id 20so114154bwz.34 for ; Wed, 18 Mar 2009 09:20:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=U/OJyeI0eXllHqjCKZVVZdxTHg8Z1EUaGfscZtCYb/o=; b=ReIASqTGTCniUjT4xx3GDGXH9qI5C7ZskfimJQ9vag+Ejck54nA3sny8lb+x2Itx93 M1fXSAKUmms7UudCDGJHv6CDt66wRm3dQ1u6SyujvLrwYDDSeOe/LgnfyXyPMuidFYTs RpZ2J5ViAsHoALPLP5vEBqWrKHnVkkDaxOjDU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=aZOuVMgJoSiXg3ottrVdFdwTfcliSyTTLz6cRRP181spBRIdSJEcEXc4juD00CPsb5 httaTdd5cNHwyG8g5euRib1el6Hvrt5Bk0J8drzZU+owC0SjsuQMTqZlHiuGIay09X1/ IyHeB1IeTiSV7JeW9vpTKAaKcx4AqP1UsmVp4= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-java@lists.gentoo.org MIME-Version: 1.0 Sender: sven.j.vermeulen@gmail.com Received: by 10.204.53.72 with SMTP id l8mr188163bkg.171.1237393235679; Wed, 18 Mar 2009 09:20:35 -0700 (PDT) In-Reply-To: References: <6b16fb4c0903171033o24820816r7708587767df899d@mail.gmail.com> Date: Wed, 18 Mar 2009 17:20:34 +0100 X-Google-Sender-Auth: 878285cc7bbca881 Message-ID: <6de0e7060903180920j55b26118gf8ae12f5941d1a4d@mail.gmail.com> Subject: Re: [gentoo-java] CPU consumed by tomcat is always 100% From: Sven Vermeulen To: gentoo-java Content-Type: multipart/alternative; boundary=001636c5b2d74298bf046567105f X-Archives-Salt: 6ffa85a1-03be-467f-b39e-645634f3a98d X-Archives-Hash: 7bdad2f022d76c77966e0a934f163314 --001636c5b2d74298bf046567105f Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, Mar 17, 2009 at 7:28 PM, Jean-No=EBl Rivasseau = wrote: > 1) Can you try to update to Tomcat 6 ? > > 2) Did you deploy any web-app in your container? If yes, the problem is > most likely due to your web-app (infinite loop most probably). > Try taking threaddumps (kill -3 ) and watch the output. Perhaps you can see from the dump where in your code (assuming it is the web applicatio= n code) the issue is. If you take several dumps sequentially (with an interval of a few seconds) you can try to parse the output with tools such as Samurai (Google for "samurai thread analyzer"). Threaddump information is usually stored in the native standard out of the java process. Wkr, Sven Vermeulen --001636c5b2d74298bf046567105f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Tue, Mar 17, 2009 at 7:28 PM, Jean-No=EBl Riv= asseau <elvanor@= gentoo.org> wrote:
1) Can you try to update to Tomcat 6 ?

2) Did you deploy any web-app= in your container? If yes, the problem is most likely due to your web-app = (infinite loop most probably).

Try taking threaddu= mps (kill -3 <pid>)=A0 and watch the output. Perhaps you can see from= the dump where in your code (assuming it is the web application code) the = issue is.

If you take several dumps sequentially (with an interval of a few secon= ds) you can try to parse the output with tools such as Samurai (Google for = "samurai thread analyzer").

Threaddump information is usua= lly stored in the native standard out of the java process.

Wkr,
=A0 Sven Vermeulen
--001636c5b2d74298bf046567105f--