maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igor Fedorenko (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MNG-4866) DefaultLegacySupport leaks MavenSession instances in some cases
Date Thu, 14 Oct 2010 17:03:32 GMT

     [ http://jira.codehaus.org/browse/MNG-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Igor Fedorenko closed MNG-4866.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0.1

Fixed in http://svn.apache.org/viewvc?view=revision&revision=1022613

> 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
>            Assignee: Igor Fedorenko
>             Fix For: 3.0.1
>
>
> 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

        

Mime
View raw message