On 20/09/2011 19:59, Dan Checkoway wrote: > Thanks for the quick reply, Mark. Much appreciated. I was afraid that was > the case. > > What I was trying to accomplish was...data that's not request/response > specific in any way, that survives requests. I was using ThreadLocal so as > to make it non-blocking, i.e. I didn't want to centralize management of this > stuff and have to synchronize access to it across my hundreds of executor > threads. > > Sounds like I'll need to bite the bullet on that. Oh well... :-)
I assume it changes rarely (and you would have had to deal with that even if using ThreadLocals and had the same concurrency issues). A read/write lock should do the trick if reads >> writes. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
