https://bz.apache.org/bugzilla/show_bug.cgi?id=59138
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Mark Thomas <ma...@apache.org> ---
This has been fixed in 9.0.x for 9.0.0.M4 onwards, 8.0.x for 8.0.33 onwards,
7.0.x for 7.0.69 onwards and 6.0.x for 6.0.46 onwards.
I have down-graded this to DEBUG. After the 'fun' with the profiler I've double
checked this and also confirmed that the JRE implementation is fundamentally
the same. There is no chance of a memory leak just because the key for a
ThreadLocal was loaded by the web application.
The logging is only useful and will only serve its intended purpose (fixing
memory leaks) if it is accurate. Logging non-issues at anything above debug is
just going to annoy people.
--
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
