commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vera Mickaël (JIRA) <>
Subject [jira] Commented: (FILEUPLOAD-120) memory leak due to classloader leak (in
Date Fri, 17 Nov 2006 14:16:38 GMT
    [ ] 
Vera Mickaël commented on FILEUPLOAD-120:

I don't feel like my issue is invalid. 

This is really a commons.fileupload bug as commons.fileupload depends on a lib that isn't
designed to be embeded in a webapp.

I did open an issue in commons.fileupload because I expected developpers of fileuploads to
be concerned by hot deploy in web servers more than Could someone of the commons.fileupload
support my issue in by voting for it in, and add a comment supporting
my description of the problem. 

This a complex problem with a very simple solution, any support for the team is

> memory leak due to classloader leak (in
> ---------------------------------------------------
>                 Key: FILEUPLOAD-120
>                 URL:
>             Project: Commons FileUpload
>          Issue Type: Bug
>    Affects Versions: 1.1.1
>         Environment: JBoss portal
>            Reporter: Vera Mickaël
> opens a thread that is never stopped. The result is that a reference from
a container class (jboss threads pool) to my webapp classloader is never released and my webapp
classloader is never garbaged. After serveral deploy/undeploy cycles I experience an "OutOfMemoryError
: PermGen".
> I did open an issue in :
> I also open an issue here as I think commons.fileupload have concerns about webapp environnements

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