Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 89327 invoked from network); 5 Apr 2011 16:28:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Apr 2011 16:28:04 -0000 Received: (qmail 74158 invoked by uid 500); 5 Apr 2011 16:28:00 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 74089 invoked by uid 500); 5 Apr 2011 16:28:00 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 74080 invoked by uid 99); 5 Apr 2011 16:28:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Apr 2011 16:28:00 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [212.227.17.10] (HELO moutng.kundenserver.de) (212.227.17.10) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Apr 2011 16:27:51 +0000 Received: from kali.localnet (p549C901D.dip0.t-ipconnect.de [84.156.144.29]) by mrelayeu.kundenserver.de (node=mreu3) with ESMTP (Nemesis) id 0Mepp6-1QI6NG3rlw-00OI3B; Tue, 05 Apr 2011 18:27:31 +0200 From: Michael Jerger Organization: IB Jerger To: "Tomcat Users List" Subject: Re: How to limit tomcats thread consumption? Date: Tue, 5 Apr 2011 18:27:25 +0200 User-Agent: KMail/1.13.5 (Linux/2.6.32-26-generic; KDE/4.5.3; i686; ; ) References: <201104041643.42245.jerger@jerger.org> <4D9B0932.70407@ice-sa.com> <4D9B3D0C.3010906@apache.org> In-Reply-To: <4D9B3D0C.3010906@apache.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1462027.cbc60aRQRB"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201104051827.29632.jerger@jerger.org> X-Provags-ID: V02:K0:ulz9kP/7+juJWyAKmf1rULfcOFYbCVoQ6tTh4/5kC0g HqK7BaQmq3ulXYAhZjkVG4zPgCiY29D2Yl2UKHuFBz7qOdnvpm anh4jP5EhhPECddmdxy584jiGuXOOHAIDyEmD5F8vCjpzahnTc ELYXkJtkxjaGc4x1l607OcoZfoE9aufNSW9b2wUYd49d0glNzL Vx+bo4kH3acdmiy00sxc45BwoGe14lB/upfsLNLxFQ= X-Virus-Checked: Checked by ClamAV on apache.org --nextPart1462027.cbc60aRQRB Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Mark wrote: > On 05/04/2011 13:21, Andr=C3=A9 Warnier wrote: > > I'll split my response in 2 parts, so that the right person(s) here have > > an easier time to interject their answers/suggestions : > >=20 > > Part 1, for a tomcat expert : > >=20 > > Michael Jerger wrote: > > ... > >=20 > >> So I'm wondering why tomcat needs all these threads and whether I can > >> limit these threads ... (on my system tomcat runs as java). It seams > >> to me that my tomcat rus about 50 threads in idle mode ... thats quite > >> a lot. > >=20 > > It does seem quite a lot to me too, but maybe someone else can give a > > clue. >=20 > Seems high to me too. A thread dump will explain what is going on. =46ound the answer allready - in the deployed webapp (liferay) is a c3po - = db- connection pool used.=20 Due to another bug (concerning spring and c3po) the configuration was not=20 handeld correctly at this point - so there was the default configuration in= =20 place. Default configuration means maxPoolSize =3D 100 - and every pooled db-conne= ction=20 uses an own thread. So these high thread count had not much to do with tomc= at=20 but with the app deploed within - sorry for that. But discussing with Andre lead me to the right point - I used another way o= f=20 configuration for c3po - now threads are under controll - thank u very much= =20 :-)). Michael --nextPart1462027.cbc60aRQRB Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAk2bQu0ACgkQGizPrwyMK7adLQCg2/kbKzpSfwWY4RChVMgw4KEZ ZVAAnjCLz6gWjc0X8ltBimpc6XHSJ+om =NhhF -----END PGP SIGNATURE----- --nextPart1462027.cbc60aRQRB--