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.161.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=LFSBJ/NkCZG5giQbHaDwgvNIZYypp09eL0bqaFBoUmMBt1CzZ98deuRnnC3y1F/yuR
         TkutqVYV6fG2Cmy3XIjduZ3or/oXFwF27eVdgfEXg4ZmNBW0cVEjLXyGYdDrGz9kGig+
         i+6/XM1aoESJ/1zrnkzbgSjCSXgOfskGTarMU=
MIME-Version: 1.0
In-Reply-To: <4DF38598.3010702@kippdata.de>
References: <BANLkTinWfM9kg9Bc2SbMXK0FJvftRHFHGw@mail.gmail.com>
 <99C8B2929B39C24493377AC7A121E21FAFF0860FA2@USEA-EXCH8.na.uis.unisys.com>
 <BANLkTikL6hAUnTedCqDXOE_s0R087ZbGHA@mail.gmail.com>
 <BANLkTim9b52=jmQ4uPUpyMmgaA0MBVmDfA@mail.gmail.com>
 <4DF38598.3010702@kippdata.de>
From: Afkham Azeez <afkham@gmail.com>
Date: Sat, 11 Jun 2011 22:53:08 +0530
Message-ID: <BANLkTimo1UG_CGJMeKqpGZYQdo7ZoZTfRg@mail.gmail.com>
Subject: Re: Terminating long running request threads
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=00248c6a8466c831be04a572f152

--00248c6a8466c831be04a572f152
Content-Type: text/plain; charset=ISO-8859-1

Thanks Rainer. I think I can use the RequestProcessor MBeans.

Thanks
Azeez

On Sat, Jun 11, 2011 at 8:41 PM, Rainer Jung <rainer.jung@kippdata.de>wrote:

> 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
>
>

--00248c6a8466c831be04a572f152--