[ http://issues.apache.org/jira/browse/FILEUPLOAD-120?page=comments#action_12451381 ] Vera Mickaël commented on FILEUPLOAD-120: -----------------------------------------
I proposed a solution on commons.io, an API using the classloader to release resources. I thought that maybe commons.fileupload may offer the same service and delegate a part of it to commons.io. As I don't use directly commons.io, I'd prefer to ask commons.fileupload to release its resources better than to commons.io Thanks for reopening this issue, IMHO the new status reflects better the situation. > 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 > > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
