[ http://issues.apache.org/jira/browse/IO-99?page=comments#action_12450870 ] Henri Yandell commented on IO-99: ---------------------------------
Thanks for the reply Vera; please don't take my comment as a negative view. Definitely a good idea to bring it up to the FileUpload guys too - both IO and FileUpload are looking to do a new release soon and the question of whether this should hold up those releases should be asked. I'll bring that up on the commons-dev@ mailing list. > FileCleaner thread never ends and cause memory leak in AS > --------------------------------------------------------- > > Key: IO-99 > URL: http://issues.apache.org/jira/browse/IO-99 > Project: Commons IO > Issue Type: Bug > Affects Versions: 1.2 > Environment: JBOssPortal with commons.fileupload > Reporter: Vera Mickaël > Priority: Critical > > FileCleaner opens a thread and no solution is given to the user to end it. So > when an application is undeployed > in an Application Server, a thread is still alive. The WebApp can't be > undeployed and this results in a classloader > leak that will cause an OutOfMemoryError. > I think the API should be extended so that a user can end the thread. A > better way would be to provide a class that > cleans everything for commons IO. -- 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]
