You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Jochen Wiedmann (JIRA)" <ji...@apache.org> on 2007/01/02 21:09:27 UTC
[jira] Resolved: (FILEUPLOAD-120) memory leak due to classloader
leak (in commons.io)
[ http://issues.apache.org/jira/browse/FILEUPLOAD-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Wiedmann resolved FILEUPLOAD-120.
----------------------------------------
Resolution: Fixed
Ok, IO-99 is resolved, Henri's patch is in, so I am now resolving this issue.
> memory leak due to classloader leak (in commons.io)
> ---------------------------------------------------
>
> Key: FILEUPLOAD-120
> URL: http://issues.apache.org/jira/browse/FILEUPLOAD-120
> Project: Commons FileUpload
> Issue Type: Bug
> Affects Versions: 1.1.1
> Environment: JBoss portal
> Reporter: Vera Mickaël
> Fix For: 1.2
>
> Attachments: FileCleanerCleanup.java
>
>
> commons.io opens a thread that is never stopped. The result is that a reference from a container class (jboss threads pool) to my webapp classloader is never released and my webapp classloader is never garbaged. After serveral deploy/undeploy cycles I experience an "OutOfMemoryError : PermGen".
> I did open an issue in commons.io : https://issues.apache.org/jira/browse/IO-99
> I also open an issue here as I think commons.fileupload have concerns about webapp environnements
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org