Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DD0466617 for ; Thu, 9 Jun 2011 17:19:11 +0000 (UTC) Received: (qmail 58598 invoked by uid 500); 9 Jun 2011 17:19:08 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 58413 invoked by uid 500); 9 Jun 2011 17:19:08 -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 58404 invoked by uid 99); 9 Jun 2011 17:19:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Jun 2011 17:19:08 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of afkham@gmail.com designates 209.85.213.45 as permitted sender) Received: from [209.85.213.45] (HELO mail-yw0-f45.google.com) (209.85.213.45) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Jun 2011 17:19:00 +0000 Received: by ywl41 with SMTP id 41so1370546ywl.18 for ; Thu, 09 Jun 2011 10:18:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=mOU601IQcWtT35noi54W/flmi6C4Nw49oxUZNvl+j7A=; b=qzSg6/dMMPJO6IWs55xyP/LZEY7V0/wMCt82aLRWYc66zu9H+IbIB5H7cxW/hj7cYw Q8uP77ActO+HX7BC3sesKNMQVi8ogiiSJKtcGKHTm4FkH8yjSelVTOuzYQEAVUhuemf4 hpA18V+5uuc6FMdiGZ8xv18CRDBqz6x8oM1uE= 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=VIKysJX6GvL399cU5SRRGGT22J1I9iD7ML/Y+vJCl4fqCBMjqO51ncGlvsWG6pFoZH HR1fYRMrQcOjPnD25lRwGXKA4B4/2ibfiZ57tg0c2uWiS9Oe/iN/FYIupS9LujH7osE8 QdaDUZIZ3XcuVhF/cx/Vfd10qRWVjiXEzULwM= Received: by 10.236.63.136 with SMTP id a8mr1398445yhd.339.1307639864700; Thu, 09 Jun 2011 10:17:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.236.202.41 with HTTP; Thu, 9 Jun 2011 10:17:24 -0700 (PDT) In-Reply-To: References: From: Afkham Azeez Date: Thu, 9 Jun 2011 22:47:24 +0530 Message-ID: Subject: Re: Terminating long running request threads To: Tomcat Users List Content-Type: multipart/alternative; boundary=00248c6a8466a1303404a54aa189 X-Virus-Checked: Checked by ClamAV on apache.org --00248c6a8466a1303404a54aa189 Content-Type: text/plain; charset=ISO-8859-1 For our requirement, it is even OK to detect to which webapp such a request is coming, and unload that webapp. On Thu, Jun 9, 2011 at 10:33 PM, Afkham Azeez wrote: > Hi folks, > We are using embedded Tomcat 7.0.14, and we have a requirement to somehow > terminate request threads that have been running for a 'long' time. Does > Tomcat provide any support to do this? Do we have access to the request > thread pool through JMX, and if so, is there a way to get hold of these long > running threads & terminate them? > > Thanks > Azeez > --00248c6a8466a1303404a54aa189--