commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Wiedmann (JIRA)" <>
Subject [jira] Commented: (IO-99) FileCleaner thread never ends and cause memory leak in AS
Date Thu, 28 Dec 2006 23:59:23 GMT
    [ ] 
Jochen Wiedmann commented on IO-99:

I have reviewed Stephen's patch and it looks good to me. Only minor note:  I'd recommend to
make getTrackCount() synchronized.

Can we close this issue now and proceed with releasing 1.3?

> FileCleaner thread never ends and cause memory leak in AS
> ---------------------------------------------------------
>                 Key: IO-99
>                 URL:
>             Project: Commons IO
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: JBOssPortal with commons.fileupload
>            Reporter: Vera Mickaƫl
>            Priority: Critical
>             Fix For: 1.3
>         Attachments: IO-99.patch
> 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:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message