While it is possible to do so (If I know it) wouldn't it be more elegant if Tomcat handles it automatically. It is hard to educate the users to cleanup their threadlocals
Recreating the threads in threadpool once per restart is not really expensive and users must be fine with that On Thu, Oct 16, 2008 at 2:04 PM, Leon Rosenberg <[EMAIL PROTECTED]> wrote: > Err, why can't you reset the object after usage or at next redeploy? > Leon > > On Thu, Oct 16, 2008 at 7:26 AM, Noble Paul നോബിള് नोब्ळ् > <[EMAIL PROTECTED]> wrote: >> If I store an application object in ThreadLocal and do hot deployment >> it prevents the old classloader from getting GCed . Why can't Tomcat >> refresh it's threadpool after every app restart? >> --Noble >> >> --------------------------------------------------------------------- >> To start a new topic, e-mail: users@tomcat.apache.org >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > -- --Noble Paul
