tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Alvim" <>
Subject RES: Memory Leak Solved
Date Fri, 15 Apr 2005 15:41:57 GMT
The  "Introspector.flushCaches();" in the "contextDestroyed" wasn't enough
for us...

How should we use the 'swallowOutput'? We've tried this way without results:

<Context displayName="eCompany 3.0"
         privileged="true" swallowOutput="false">


Do you have links to this "known issue"?

-----Mensagem original-----
De: Trond G. Ziarkowski []
Enviada em: sexta-feira, 15 de abril de 2005 11:08
Para: Tomcat Users List
Assunto: Re: Memory Leak Solved


don't know if you are using it, but there's also a known issue with
5.0.28 and 'swallowOutput' in the <Context> element. After I turned it
off, I haven't gotten any out of memory errors...


sysdba wrote:

>We have struggled with a memory leak in 5.0.28/5.0.30 for months. There
>been many complaints about the necessity to restart Tomcat every couple
>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.
>Tomcat web server has now run for seven days without an OOM error. The
>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:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message