You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Vera Mickaël (JIRA)" <ji...@apache.org> on 2006/11/16 19:11:37 UTC
[jira] Created: (IO-99) FileCleaner thread never ends and cause
memory leak in AS
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
[jira] Resolved: (IO-99) FileCleaner thread never ends and cause
memory leak in AS
Posted by "Stephen Colebourne (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-99?page=all ]
Stephen Colebourne resolved IO-99.
----------------------------------
Resolution: Fixed
Assignee: Stephen Colebourne
I took a look at getTrackerCount(), but its already synchronized because the list is a Vector. I added a few comments about synchronization to the file to help clarify.
Closing the call as fixed.
> 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
> Assigned To: Stephen Colebourne
> 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: 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
[jira] Commented: (IO-99) FileCleaner thread never ends and cause
memory leak in AS
Posted by "Stephen Colebourne (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-99?page=comments#action_12455206 ]
Stephen Colebourne commented on IO-99:
--------------------------------------
The simple solution is to add a method exitWhenFinished() that sets a boolean flag.
The reaper thread then checks the boolean flag to see if it should stop the thread (once all tracked objects have been dealt with)
{code}
if (exitWhenFinished && trackers.isEmpty()) {
return; // terminate thread
}
{/code}
Code can then call FileCleaner.exitWhenFinished() from their servlet destroy method.
> 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
[jira] Commented: (IO-99) FileCleaner thread never ends and cause
memory leak in AS
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (IO-99) FileCleaner thread never ends and cause
memory leak in AS
Posted by "Martin Cooper (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-99?page=comments#action_12450929 ]
Martin Cooper commented on IO-99:
---------------------------------
It would make sense to me for FileCleaner to provide a method to cleanly stop the reaper thread, and possiby another method to (re-)start it. This way, an application using Commons IO could gain control over this thread. Today, no control is provided - the thread is started automatically, and cannot be (cleanly) stopped.
In the context of Commons FileUpload, this would allow a web application to start the reaper thread at startup time (e.g. servlet or filter init) and shut it down when the web app is being stopped (e.g. servlet or filter destroy).
The question then arises of what to do by default. If we decide not to start the reaper automatically, we would be breaking backwards compatibility with the current version of IO, although I do think this would be the more sensible option.
> 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
[jira] Updated: (IO-99) FileCleaner thread never ends and cause
memory leak in AS
Posted by "Jochen Wiedmann (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-99?page=all ]
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: 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
> 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: 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
[jira] Commented: (IO-99) FileCleaner thread never ends and cause
memory leak in AS
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-99?page=comments#action_12455821 ]
Henri Yandell commented on IO-99:
---------------------------------
I've attached the code needed to FILEUPLOAD-120; if you could give that a shot Vera and let us know if it solves your problem it would be great - then we can go ahead and release IO 1.3 :)
> 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
> 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: 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
[jira] Commented: (IO-99) FileCleaner thread never ends and cause
memory leak in AS
Posted by "Jochen Wiedmann (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-99?page=comments#action_12455943 ]
Jochen Wiedmann commented on IO-99:
-----------------------------------
I have added the following section to the FileUpload docs. It seems worth mentioning here, because it confirms Martins concerns: It should be possible to take over control of the reaper thread completely. In particular, one should not be forced to use the FileCleaner classes thread.
Unfortunately, this is not the whole story. The above applies only, if
* You are using commons-io 1.3, or later.
* You are loading commons-io from your web applications
WEB-INF/lib and not from another location, for example the
common/lib directory of Tomcat. This is not unlikely, because
there are quite a few applications, which do ship commons-io.
If commons-io 1.3 is loaded from your containers class path, then
the following might occur: Suggest that you have two applications,
called A and B running. (It might as well be the same application
with two names aka servlet contexts.) Both applications are using
the <code>FileCleanerCleanup</code>. Now, if you terminate application
A, but B is still running, then A terminates B's reaper thread as
well.
In other words, you should consider carefully, whether to use
the <code>FileCleanerCleanup</code>, or not. When unsure, or if you
are happy with commons-fileupload 1.1.1, or before, then you
possibly would like to avoid it.
> 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
> 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: 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
[jira] Updated: (IO-99) FileCleaner thread never ends and cause
memory leak in AS
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-99?page=all ]
Henri Yandell updated IO-99:
----------------------------
Fix Version/s: 1.3
> 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
> 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: 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
[jira] Commented: (IO-99) FileCleaner thread never ends and cause
memory leak in AS
Posted by "Vera Mickaël (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-99?page=comments#action_12451376 ]
Vera Mickaël commented on IO-99:
--------------------------------
Thanks everybody for your interest in this issue.
I've talked about this issue with a developper mastering classloaders problems. It seems that the remaining thread surely causes a classoder leak. I think classloaders leaks will soon be a point of interest for a larger community, this issue will be benefic for commons.io.
I think is that backward compatibility is important and that you should keep the thread automatically started.
Be carrefull of several points about web containers environements :
If the lib is deployed for any reason (this is not encouraged) in the classloader of the web container, the thread is shared by all applications deployed in the container. So an application stopping the thread would have an effect on other applications. Keeping all applications deployed isolated is very important.
But shall we let responsability to developpers to know if they have to stop the thread or not ? I don't think so. I can develop a lib that uses commons.io and I want my lib to be compatible with web containers environement, as commons.filepload for example. commons.filepload don't know if commons.io has to stop the thread or not because it doesn't know where the lib has been deployed. But commons.fileupload in my opinion should provide a way to release its resources, as a developper using copmmons.filepload don't have to know that commons.io is used for encapsulation reasons.
So what is the solution ?
A common solution to this problems is to use classloaders. commons.io should provide a method to stop the thread, or better to release resources, as a user of commons.io I don't have to know about the thread. This method should take as parameter the classloader of the application requesting the resources release. If the given classloader is the same as the classloader of FileCleaner, this means that the lib has been deployed inside the war, so the thread should be stopped and all resources released. If the classloader is different, then the thread is owned by the container, so don't stop it. But release other resources associated to the given classloader (listeners, cache ...) that may cause a classloader leak.
I hope I've been clear and my clues will help you. If any question remains, don't hesitate to ask for details, I watch this thread.
> 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
[jira] Commented: (IO-99) FileCleaner thread never ends and cause
memory leak in AS
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-99?page=comments#action_12450870 ]
Henri Yandell commented on IO-99:
---------------------------------
Thanks for the reply Vera; please don't take my comment as a negative view.
Definitely a good idea to bring it up to the FileUpload guys too - both IO and FileUpload are looking to do a new release soon and the question of whether this should hold up those releases should be asked. I'll bring that up on the commons-dev@ mailing list.
> 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
[jira] Commented: (IO-99) FileCleaner thread never ends and cause
memory leak in AS
Posted by "Vera Mickaël (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-99?page=comments#action_12450687 ]
Vera Mickaël commented on IO-99:
--------------------------------
I don't know if a daemon thread prevents a classloader from being garbaged ?
I worked for several days on classloader leaks, classloaders that are never garbaged because a system class or a container class keeps a reference on the webapp classloader. In memory dumps I can see that FileCleaner thread keeps references on my webapp classloader, this thread is referenced by the JBoss thread pool wich is a container class.
I can't say if this thread is responsible for my classloader leak, my opinion is that it does (look links provided, the fist one)
But this thread adds many references to a dump that is already difficult read (I use a modified version of jhat). A service in the API stopping the thread would really simplify the task of developpers like me working on classlodaer leaks.
I will open an issue in commons.fileupload referencing this one, maybe this package have more concerns about webapp environments.
http://opensource.atlassian.com/confluence/spring/pages/viewpage.action?pageId=2669
http://blogs.sun.com/fkieviet/entry/how_to_fix_the_dreaded
Thanks to whole developpers team for their work
> 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
[jira] Commented: (IO-99) FileCleaner thread never ends and cause
memory leak in AS
Posted by "Jochen Wiedmann (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-99?page=comments#action_12461277 ]
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: 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
> 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: 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
[jira] Commented: (IO-99) FileCleaner thread never ends and cause
memory leak in AS
Posted by "Stephen Colebourne (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-99?page=comments#action_12455486 ]
Stephen Colebourne commented on IO-99:
--------------------------------------
Please review and try the latest code in SVN.
> 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
> 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: 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