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: domain of rainer.jung@kippdata.de
 designates 195.227.30.149 as permitted sender)
Message-ID: <4DF38598.3010702@kippdata.de>
Date: Sat, 11 Jun 2011 17:11:20 +0200
From: Rainer Jung <rainer.jung@kippdata.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de;
 rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Terminating long running request threads
References: 
 <BANLkTinWfM9kg9Bc2SbMXK0FJvftRHFHGw@mail.gmail.com><99C8B2929B39C24493377AC7A121E21FAFF0860FA2@USEA-EXCH8.na.uis.unisys.com>
	 <BANLkTikL6hAUnTedCqDXOE_s0R087ZbGHA@mail.gmail.com>
 <BANLkTim9b52=jmQ4uPUpyMmgaA0MBVmDfA@mail.gmail.com>
In-Reply-To: <BANLkTim9b52=jmQ4uPUpyMmgaA0MBVmDfA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit

On 11.06.2011 09:30, Afkham Azeez wrote:
> Folks,
> Is there any API to get hold of Tomcat's Connector thread pools?

Each request is registered with an MBean in the MBeanServer.
As long as the request is running, the MBean contains additional info,
like the URI, when the request started, the thread name etc.

This gives you enough info to find long running requests and to find the
thread. But there's no non-deprecated Java API known to have no side
effects to terminate a thread. If it were (or you find one), we had to
check how the thread pool behaves w.r.t. "vanishing" threads.

Regards,

Rainer

> 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


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