On Friday 15 May 2009 16:58:55 Caldarale, Charles R wrote:
> > From: Rainer Frey (Inxmail GmbH) [mailto:rainer.f...@inxmail.de]
> > Subject: Re: Change thread name of HTTP worker threads at Runtime
> >
> > I just read this up. It says "should ensure". How strong t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer,
On 5/15/2009 10:47 AM, Rainer Frey (Inxmail GmbH) wrote:
> On Friday 15 May 2009 16:07:11 Christopher Schultz wrote:
>> Not likely, since Java doesn't support continuations.
>> The request handler thread should handle the request from start t
> From: Rainer Frey (Inxmail GmbH) [mailto:rainer.f...@inxmail.de]
> Subject: Re: Change thread name of HTTP worker threads at Runtime
>
> I just read this up. It says "should ensure". How strong this is
> sepends on whether this has RFC "SHOULD" characteristic
On Friday 15 May 2009 16:07:11 Christopher Schultz wrote:
> Rainer,
>
> On 5/15/2009 2:37 AM, Rainer Frey (Inxmail GmbH) wrote:
> > is the assumption that one request is processed by one thread (and never
> > passed to another during processing) true for all connectors, including
> > NIO?
>
> Are y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer,
On 5/15/2009 2:37 AM, Rainer Frey (Inxmail GmbH) wrote:
> is the assumption that one request is processed by one thread (and never
> passed to another during processing) true for all connectors, including NIO?
Are you asking if the request i
On Wednesday 06 May 2009 12:42:09 Ronald Klop wrote:
> Op woensdag, 6 mei 2009 11:58 schreef "Rainer Frey (Inxmail GmbH)" :>
>
> > Hi,
> >
> > I occassionally have to analyse thread dumps of tomcat servers which
> > serve up to 25 instances of the same (quite complex) web service
> > application.
Hi,
At the company I work we are doing this for a couple of years already with
Tomcat 4, 5 and now 6. Works very well. And makes threaddumps more easy to read.
A filter is very ease to make.
public class ThreadNameFilter implements javax.servlet.Filter {
public void doFilter(ServletRequest re
Hi,
I occassionally have to analyse thread dumps of tomcat servers which serve up
to 25 instances of the same (quite complex) web service application. All
custom threads have names that contain the instance id, but it is impossible
to see which HTTP processor threads serve which application ins