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
Tomcat Users List
users@tomcat.apache.org:
Subject: Re: Memory leak from threadlocal for hot deployment
Date: Fri Oct 17 08:19:11 CEST 2008
From: Noble Paul നോബിള് नोब्ळ् [EMAIL PROTECTED]
While it is possible to do so (If I know it) wouldn't it be more
elegant if Tomcat handles
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Noble,
Noble Paul നോബിള് नोब्ळ् wrote:
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.
They must be educated.
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
