Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
From: Jeffrey Janner <Jeffrey.Janner@PolyDyne.com>
To: 'Tomcat Users List' <users@tomcat.apache.org>
Subject: RE: Limiting threads per context
Thread-Topic: Limiting threads per context
Thread-Index: AQHN6b8batjXhJeW/0aNHAQIY8Hfdpg3rCiA
Date: Thu, 3 Jan 2013 14:43:51 +0000
Message-ID: 
 <7215BA462D00D343B2837F9113F0131F01277FD695@POSTOFFICE02.polydyne.com>
References: 
 <OF613C9BBF.4BABC500-ON86257AE8.004DF04D-86257AE8.004FC460@LocalDomain>
In-Reply-To: 
 <OF613C9BBF.4BABC500-ON86257AE8.004DF04D-86257AE8.004FC460@LocalDomain>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-SEF-7853D99-ADF1-478E-8894-213D316B8FFA: 1
X-SEF-Processed: 7_2_0_00504__2013_01_03_08_49_57
X-Virus-Checked: Checked by ClamAV on apache.org

> -----Original Message-----
> From: kharper2@oreillyauto.com [mailto:kharper2@oreillyauto.com]
> Sent: Thursday, January 03, 2013 8:31 AM
> To: users@tomcat.apache.org
> Subject: Limiting threads per context
>=20
>=20
> Hello All,
>=20
> Yesterday we had a Tomcat6 server reach maxThreads and stay that way
> until we restarted it.  After researching a thread dump and some log
> files, we found one of the applications is creating
> NullPointerExceptions and subsequently leaving a TP-ProcessorX in
> WAITING state indefinitely for a DB closePreparedStatement return.  As
> more requests come in for this application threads are being
> established and put into BLOCKED state, waiting on TP-ProcessorX.
> Eventually, the server hits maxThreads and stops serving requests
> almost entirely.
>=20
> Obviously the application causing this needs to (and is being) fixed.
> But I'm curious if there is a higher level of protection that could be
> implemented to help protect the other applications (contexts) on this
> server?  For example, is there a way to specify that a context can only
> use X number of request threads?  Or perhaps X number of threads from
> an executor?  Et cetera.
>=20
> I haven't seen anything in the docs that would do this, but it never
> hurts to ask.  Here's our server info in case it's helpful:
> OS: Ubuntu 12.04 64-bit
> Front-end Server: Apache 2.2.22 (mod_ajp to back-end via Balancer
> setup) Back-end App Server:  Tomcat 6.0.24 (AJP & HTTP connectors, no
> executor) Java -version output:
>   java version "1.6.0_20"
>   OpenJDK Runtime Environment (IcedTea6 1.9.13)
> (6b20-1.9.13-0ubuntu1~10.04.1)
>   OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)
>=20
>=20
> Thanks,
> Kyle Harper
>=20

Kyle -
Processor threads are tied to connectors, either directly or via executors.=
  Therefore, if these are all contexts under one host, or you are sharing t=
he connector (IP/port pair) for multiple hosts, I don't think there is anyt=
hing you can do.
However, since you are front-ending with apache, you might be able to set u=
p multiple connectors (IP/port pair) on the Tomcat server and use the front=
 end to direct each context to a different connector.  In this case, you ca=
n probably ignore setting up the executors, since you are not going to be s=
haring threads between the contexts.
Jeff


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org