commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IO-99) FileCleaner thread never ends and cause memory leak in AS
Date Thu, 16 Nov 2006 18:53:44 GMT
    [ http://issues.apache.org/jira/browse/IO-99?page=comments#action_12450487 ] 
            
Henri Yandell commented on IO-99:
---------------------------------


The static initializer for FileCleaner:

    static {
        reaper.setPriority(Thread.MAX_PRIORITY);
        reaper.setDaemon(true);
        reaper.start();
    }

Do daemon threads cause problems in undeploys?

> 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message