This one of the remedies proposed. There is also a bug reported, and a patch
for it. Finally you can try swallowOutput=false in your context.xml.
Pedro Nevado
De: sysdba [EMAIL PROTECTED]
Enviado: viernes, 15 de abril de 2005 15:49
Para: Tomcat Users List
Asunto: Memory Leak Solved
We have struggled with a memory leak in 5.0.28/5.0.30 for months. There have
been many complaints about the necessity to restart Tomcat every couple days
due to Out of Memory errors, but no solutions that cured it. Well, the
suggestion to put the single line:
Introspector.flushCaches();
in the destroy method of a servlet in a redeployable app finally solves it.
Our
Tomcat web server has now run for seven days without an OOM error. The
amount
of time spent with the Optimizeit profiler trying to locate a nonexistent
memory leak in the application code cannot be overestimated. This discovery
should be bold red lettered in the docs.
Gary Harris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
