Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <11769110.1187883150544.JavaMail.jira@brutus>
Date: Thu, 23 Aug 2007 08:32:30 -0700 (PDT)
From: "Vera Mickael (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Updated: (FILEUPLOAD-144) Parameters values are lost
In-Reply-To: <13148704.1187882790596.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vera Mickael updated FILEUPLOAD-144:
------------------------------------

    Attachment: test.fileupload.zip

This project reproduces the problem on my platform on two computers. 

Just build the war with the build.xml ant file, the war is generated in the 'war' directory. The deploy the war in tomcat or jboss with assertions activated.

Access webapp with the url http://loclahost:8080/test.fileupload

Click the submit button at the end of the page, most of times an assertion is thrown and it should not. 

> 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: 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. 

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