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. All custom threads have names that contain the instance id, > > but it is impossible to see which HTTP processor threads serve which > > application instance. > > > > Now we came up with the idea to rename the threads at the beginning of > > the request processing (to current-name + application-id), and rename > > them back totheir base name after the request is processed. As these > > threads are managed by Tomcat, I am wondering: is this a bad idea? > > Anything in Tomcat (or Java) that could cause a problem if we do that? > > 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. > > Ronald.
Thanks for confirming, I implemented this and it works fine. I wonder though: is the assumption that one request is processed by one thread (and never passed to another during processing) true for all connectors, including NIO? Regards Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
