Are you using Commons Logging or a package that uses it (e.g.
Velocity)? It is notorious for holding onto its own classloader,
which will hold a copy of any and all classes that have been loaded.
I'm still working on slaying that dragon in one of my production apps.
...Richard
On Oct 28, 2005, at 5:10, Paolo Donà wrote:
On 10/28/05, ausias vives <[EMAIL PROTECTED]> wrote:
Exactly, what I was saying is that if you get OOMEs
only after reloading the application several times is
most likely to be related with some tomcat issues. [cut]
I just switched my tapestry4 app from Tomcat 5028 to Bea Weblogic
8.1 SP2
and I'm experiencing the same reloading OOME issues I had with
tomcat...
So it doesn't seem a tomcat bug. I'm running with tapestry caching
enabled.
I'll dig more but I'm pretty sure it's not my app fault.
Paolo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
