DefaultLegacySupport leaks MavenSession instances in some cases
---------------------------------------------------------------
Key: MNG-4866
URL: http://jira.codehaus.org/browse/MNG-4866
Project: Maven 2 & 3
Issue Type: Bug
Affects Versions: 3.0
Reporter: Igor Fedorenko
When DefaultLegacySupport is used in conjunction with thread pools
(ThreadPoolExecutor for example), MavenSession instance is essentially leaked
via InheritableThreadLocal used by DefaultLegacySupport and will not be
released to garbage collection until pooled thread is stopped and it's thread
locals are cleaned up. This can result in excessive memory usage because repo
system cache can be quite big. See also MNG-4860
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira