https://issues.apache.org/bugzilla/show_bug.cgi?id=41059
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
--- Comment #14 from Mark Thomas <ma...@apache.org> 2009-07-17 10:30:38 PST ---
This has been fixed in trunk and proposed for 6.0.x and 5.5.x
Keep in mind that ENABLE_CLEAR_REFERENCES=true is intended to:
a) work around GC issues in old JVMs (unlikely to an issue with current jvms)
b) work around one source of memory leaks in webapps that are buggy or use
buggy libraries
The very nature of the ENABLE_CLEAR_REFERENCES code is that it is likely to
cause problems - as it does with log4j. Whilst this patch (thanks for the patch
by the way) will reduce the chances or seeing errors, it will not eliminate
them.
A better approach is to set ENABLE_CLEAR_REFERENCES=false and to use a profiler
to identify and fix the root causes of any memory leaks. A well-written app
using well behaved libraries should not need ENABLE_CLEAR_REFERENCES=true
If when doing this you find a memory leak in the Tomcat code (hopefully you
won't - all the ones we know about should be fixed) then please open a new
Bugzilla entry and report it.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
