[
https://issues.apache.org/jira/browse/FILEUPLOAD-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598206#comment-13598206
]
Thomas Neidhart commented on FILEUPLOAD-205:
--------------------------------------------
I think it would make sense to add a "forceExit" or "forceCleanup" method to
the FileCleaningTracker, which processes all remaining trackers and terminates
the reaper. This method should be called in the
FileCleanerCleanup.contextDestroyed method to make sure we really cleanup
everything and do not have to rely on the objects being gc'ed properly when the
context is destroyed.
> 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
