Am 2013-05-21 20:38, schrieb Mark Thomas:
Seems like they understood the problem. But I do doubt that this is a
fixed size moemory leak.
I think the point they are trying to make is that it is only the first
instance of the web application to be unloaded that will be pinned in
memory. Subsequent reloads won't trigger a leak. That is correct.
Does this mean that only one WebAppClassLoader stays in memory because
the thread is launched once and attached to that class loader?
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
