You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Thomas Neidhart (JIRA)" <ji...@apache.org> on 2013/03/10 12:01:12 UTC
[jira] [Commented] (FILEUPLOAD-205) FileCleaningTracker Reaper
thread not ended
[ https://issues.apache.org/jira/browse/FILEUPLOAD-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598205#comment-13598205 ]
Thomas Neidhart commented on FILEUPLOAD-205:
--------------------------------------------
This is maybe related to this question at stackoverflow:
http://stackoverflow.com/questions/12301934/org-apache-commons-io-filecleaningtracker-does-not-delete-temp-files-unless-expl
It looks like in some environment, the DiskFileItem references are not gc'ed and thus the FileCleaningTracker has still trackers attached, thus the Reaper thread will not end after a call to exitWhenFinished (he is not finished yet).
> FileCleaningTracker Reaper thread not ended
> -------------------------------------------
>
> Key: FILEUPLOAD-205
> URL: https://issues.apache.org/jira/browse/FILEUPLOAD-205
> Project: Commons FileUpload
> Issue Type: Bug
> Affects Versions: 1.2.2
> Environment: Tomcat 6, JDK 1.6.0_21
> Reporter: Philip Helger
> Assignee: Jochen Wiedmann
>
> When using a new FileCleaningTracker and calling exitWhenFinished upon WebApp context deinitialization the thread is not shutdown. This can be easily reproduced by using Tomcat's "Find leaks" funcitonality.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira