[ http://issues.apache.org/jira/browse/FILEUPLOAD-120?page=comments#action_12450746 ] Vera Mickaël commented on FILEUPLOAD-120: -----------------------------------------
I don't feel like my issue is invalid. This is really a commons.fileupload bug as commons.fileupload depends on a lib that isn't designed to be embeded in a webapp. I did open an issue in commons.fileupload because I expected developpers of fileuploads to be concerned by hot deploy in web servers more than commons.io Could someone of the commons.fileupload support my issue in commons.io by voting for it in commons.io, and add a comment supporting my description of the problem. This a complex problem with a very simple solution, any support for the commons.io team is welcome. > 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]
