You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Purushottam M. Nawle (JIRA)" <ji...@apache.org> on 2008/08/14 11:33:44 UTC

[jira] Updated: (FILEUPLOAD-59) [fileupload] Memory Issue

     [ https://issues.apache.org/jira/browse/FILEUPLOAD-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Purushottam M. Nawle updated FILEUPLOAD-59:
-------------------------------------------

    Attachment: UploadTest.zip

Attached is the zip file containing a sample application using commons file upload. The lib directory contains a jar file named "commons-fileupload-ext.jar" resolves the out of memory problem. The new version of FileItem treats the plain text form parameters and multipart parameter in different ways. The newer version uses StringBuffer for the plain text parameters. This FileItem also supports ajax based monitoring of the file upload.

> [fileupload] Memory Issue
> -------------------------
>
>                 Key: FILEUPLOAD-59
>                 URL: https://issues.apache.org/jira/browse/FILEUPLOAD-59
>             Project: Commons FileUpload
>          Issue Type: Bug
>    Affects Versions: 1.0 Final
>         Environment: Operating System: All
> Platform: All
>            Reporter: Vimil Saju
>         Attachments: UploadTest.zip
>
>
> 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.