> -----Original Message----- > From: Rodrigo Ruiz [mailto:[EMAIL PROTECTED] > Sent: Friday, December 05, 2003 2:52 PM > To: Tomcat Users List > Subject: Re: Tomcat's ThreadPool and InheritableThreadLocal variables > > > AFAIK, Java does not provide any way to clear ThreadLocal variable > values related to a given thread. As it is a language-level limitation, > Tomcat can do nothing to resolve it. I tend to think that this is also a > valid reason to consider not necessary to document it ;-) > > Cheers, > Rodrigo Ruiz
Fair enough. :) But,still,it would be good to have it documented somewhere with a note which says it's a language level limitation. ;) > > > In some ways,you are right.But,looking at it this way. > > > >When it's said that each request is processed in a *new* thread,it is > >reasonable to expect that thread-specific language constructs will be > >handled.In this case,a new thread would mean new copies of > ThreadLocal and > >InheritableThreadLocal variables. > > If this new thread is created in a customized manner(in this > case,alloted > >from a ThreadPool),I would say that the behaviour of the new > Thread should > >be modelled on the language defined lines. > > It would be good if this is atleast documented somewhere. :) > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
