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

Laurent Goncalves updated FILEUPLOAD-144:
-----------------------------------------

    Attachment: test.fileupload.zip

Project modified containing unit tests for reproducing the problem.
Unit tests are in the test/src source folder.
Unit tests can be started from eclipse environment.
File upload modified sources are in the src_fileupload folder.
In this version the MultipartStream is modified, you can restore the old 
version of the makeAvailable() method, the old method is commented.
With the new version of MultipartStream, all test case are successfull, if you 
restore the old version of the makeAvailable() method you will see failures.

> Parameters values are lost
> --------------------------
>
>                 Key: FILEUPLOAD-144
>                 URL: https://issues.apache.org/jira/browse/FILEUPLOAD-144
>             Project: Commons FileUpload
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: JBoss 4 / XP / Servlet / both Firefox and IE
>            Reporter: Vera Mickael
>            Priority: Critical
>         Attachments: MultipartStream.java, test.fileupload.zip, 
> test.fileupload.zip
>
>
> When parsing a request with the streaming API, some parameters loose their 
> values. I can easily reproduce the problem when a lot of parameters are 
> submitted (about 400 in a table). My code is as follows :
>             final FileItemStream itemStream = anItemIterator.next();
>             final String fieldName = itemStream.getFieldName();
>             System.out.print("Field " + fieldName);
>             InputStream stream = itemStream.openStream();
>             final String value = Streams.asString(stream, "UTF-8");
> The last statement sometimes returns a value and sometimes not. Sometimes I 
> can retreive all parameters, sometimes I loose 3 or 4 parameters. I 
> reproduced the problem on two computers. I have a very small application with 
> a servlet of 69 lines that reproduces the problem, the project is attached to 
> this issue. 

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

Reply via email to