On 6/18/06, Cliff Zhao <[EMAIL PROTECTED]> wrote:
Tapestry jar files are in my war files.
That is then surprising... Why would you be affected with your own
ThreadLocal but not the ones from Tapestry and Hivemind (none of them are
calling ThreadLocal.remove())?
Thanks,
Henri.
Tapestry jar files are in my war files.
On 6/18/06, Henri Dupre <[EMAIL PROTECTED]> wrote:
This is very interesting... I don't have any threadlocal in my app but at
every redeployment the memory is increasing. I had a quick look at the
tapestry source code and there is a bunch of ThreadLocal.se
This is very interesting... I don't have any threadlocal in my app but at
every redeployment the memory is increasing. I had a quick look at the
tapestry source code and there is a bunch of ThreadLocal.set(null). But it
seems that in your case, they are not affecting the perm memory?
Where are you
I did some tests and the results are very promising.
I use one ThreadLocal variable in my Tapestry application. It took about
4.5MB for every re-deployment from Perm Memory and never went down. After I
changed the ThreadLocal.set(null) to ThreadLocal.remove(), the Perm Memory
was stablized at 31M
