commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Wiedmann (JIRA)" <>
Subject [jira] Updated: (IO-99) FileCleaner thread never ends and cause memory leak in AS
Date Mon, 04 Dec 2006 08:03:25 GMT
     [ ]

Jochen Wiedmann updated IO-99:

    Attachment: IO-99.patch

Proposed patch, in order to get this done (please note, that releases are waiting for this,
as Henri wrote).

After considering Martin's and Stephen's suggestions, I followed Stephen's: The possibility
to restart the thread raises, IMO, synchronization questions, which I do not want to address
right now. The evaluation, whether a restart is required and a possible implementation may
well be left for 1.4, IMO.

> 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
>         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