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? Also, is this better implemented in the servlets (almost all our relevant requests go to servlets, the are hardly any JSP) or as a filter? Filter seems a better idea, but I never developed one, so I might overlook some characteristic that makes this unsuitable to do in a filter. We want to implement this first on Tomcat 5.0, but migrate to Tomcat 6.0 later this year. Any notable differences in this regard? TIA for any thoughts on this. Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
