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 (nike.apache.org: domain of afkham@gmail.com designates
 209.85.213.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=gorjqCOz/46+rmhUGw3jylTNijGBRalnhb91bl7T/F98u50P5VCuWDobxGj/k0dVJe
         j2MYOnvbcj90ricSvZHafE5xEaNCGGhDjDo9Tw442QFXRE7w2mlCa8W2yEQB+s3dQZAP
         QcfZZZkLytVaDYmAFgyexyke6DPIRm4MT5DrQ=
MIME-Version: 1.0
In-Reply-To: <BANLkTikL6hAUnTedCqDXOE_s0R087ZbGHA@mail.gmail.com>
References: <BANLkTinWfM9kg9Bc2SbMXK0FJvftRHFHGw@mail.gmail.com>
 <99C8B2929B39C24493377AC7A121E21FAFF0860FA2@USEA-EXCH8.na.uis.unisys.com>
 <BANLkTikL6hAUnTedCqDXOE_s0R087ZbGHA@mail.gmail.com>
From: Afkham Azeez <afkham@gmail.com>
Date: Sat, 11 Jun 2011 13:00:56 +0530
Message-ID: <BANLkTim9b52=jmQ4uPUpyMmgaA0MBVmDfA@mail.gmail.com>
Subject: Re: Terminating long running request threads
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=20cf300facb9eb364a04a56aabd2

--20cf300facb9eb364a04a56aabd2
Content-Type: text/plain; charset=ISO-8859-1

Folks,
Is there any API to get hold of Tomcat's Connector thread pools?

Regards
Azeez

On Thu, Jun 9, 2011 at 10:58 PM, Afkham Azeez <afkham@gmail.com> wrote:

>
>
> On Thu, Jun 9, 2011 at 10:51 PM, Caldarale, Charles R <
> Chuck.Caldarale@unisys.com> wrote:
>
>> > From: Afkham Azeez [mailto:afkham@gmail.com]
>> > Subject: Terminating long running request threads
>>
>> > is there a way to get hold of these long running threads
>> > & terminate them?
>>
>> This is not an issue specific to Tomcat; there is no way to safely
>> terminate a Java thread without the cooperation of that thread.  Best if you
>> can code your webapp so that your request processors periodically check if
>> they've been running too long and give up if so.
>>
>
> Yes, it is not a Tomcat specific issue. The thing is, we don't have total
> control over what type of webapps will be deployed. We do restrict certain
> operations using a Java Security Manager, but I do not think we can restrict
> the running time of a Thread using a security manager. Using
> the ThreadMXBean we can monitor the time each thread takes, and get the
> thread IDs of long running threads. It may be possible to get that thread to
> terminate if we have some support for that from the Tomcat threadpool. Just
> thinking out loud.
>
> Thanks
> Azeez
>

--20cf300facb9eb364a04a56aabd2--