Thanks again. This has been a very enlightening thread (no pun intended).
Caldarale, Charles R wrote: > > Normally, there's a thread pool per <Connector>. Tomcat 6 introduces > the ability to share thread pools across multiple <Connector>s, via the > <Executor> element. (I haven't tried it.) > When might an advanced Tomcat user need to play with this Executor element? In what ways could you potentially make use of sharing a thread pool between all connector versus for only a single connector? What kinds of requirements would make someone place an Executor element in their server.xml? Yes, that's another reason to restrict the lifetime to that of a single > request. Exposure across webapps would be difficult to exploit unless > the class definition of the object cached via ThreadLocal were visible > to both webapps. Good point. If the same class definition were in fact placed in the classpath of both applications, wouldn't this still not work though - because they'd be loaded by the web context-specific classloaders and therefore not be the "same" class? (i.e. because they'd fail the instanceof test) If that's the case, would it work if the class were placed in the CATALINA_HOME/lib instead? -- View this message in context: http://www.nabble.com/Is-ThreadLocal-safe-to-use-in-servlets-tf3858168.html#a11270711 Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
