commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Wiedmann (JIRA)" <>
Subject [jira] Commented: (FILEUPLOAD-59) [fileupload] Memory Issue
Date Thu, 28 Jun 2007 06:40:26 GMT


Jochen Wiedmann commented on FILEUPLOAD-59:

I see absolutely no reason, why we should still support 1.1. This applies, in particular,
to memory considerations and stuff like that. The streaming API was invented exactly for that

> [fileupload] Memory Issue
> -------------------------
>                 Key: FILEUPLOAD-59
>                 URL:
>             Project: Commons FileUpload
>          Issue Type: Bug
>    Affects Versions: 1.0 Final
>         Environment: Operating System: All
> Platform: All
>            Reporter: Vimil Saju
> The reason for out of memory exception is that a FileItem object is created for 
> each request parameter whether it is file or an ordinary string parameter. the 
> FileItem object has a field of type DeferredFileStream which is initialized to 
> 262144 bytes (256 Kb) so if there are around 1000 request parameters, around 
> 256 MB of space will be required to hold the request parameters even though 
> most parameters may require only 8 to 10 bytes of memory for storage.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message