Hi. Thanks to everybody (specially to Robert) for the help. I moved to the previous version of the isapi redirector (isapi_redirect 1.2.5) and everything works perfect.
The redirector seems to have the same functionality than the newer version (perhaps the newer one has better performance?), and the upload works cool, so it is possible to move to the old version without causing problems for the rest of the applications.
Thanks


Mart�n



Hertenstein Alain writes:

Martin : I fully agree with you, the problem seems to be in the connector, as this is the main config difference between both servers we use here.
Robert, thanks a lot for the link.


Unfortunately we use the ISAPI redirector 2 and we -cannot- change into the older version (IIS is on a production server and the company won't agree to change its current configuration at all since there are other applications also working with this setup).

So now, what can we do to have this problem resolved ?
Will there be a fix on the redirector v2 or something ?


Thanks a lot,
Alain


-----Message d'origine-----
De : Robert Priest [mailto:[EMAIL PROTECTED] Envoy� : jeudi, 19. f�vrier 2004 20:28
� : 'Jakarta Commons Users List'
Objet : RE: FileUploadException



you may want to take a look at this info:


http://issues.apache.org/bugzilla/show_bug.cgi?id=25598

-----Original Message-----
From: Martin Marchetta [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 19, 2004 11:09 AM
To: Jakarta Commons Users List
Subject: Re: FileUploadException



That's the exact error I get (I was starting to think that I am the only one


that have the problem).
I have traced the source code of the FileUpload API, and It's ok. And If you


try to do the upload directly over tomcat (without passing through the IIS) it works perfect.
Taking into account that I logged the streams generated by the browsers, and


that these streams are ok, at this point there are 2 possibilities: the problem is the IIS, or the ISAPI redirector.
I think that the problem is de ISAPI redirector.
Anybody knows a way to see what is the isapi_redirector2.dll passing to Tomcat?
Or, better than that, a way to see what is receiving the isapi filter?


Thanks




Hertenstein Alain writes:


Hi to all,

I've used until now the "fileupload 1.0rc1" API successfully on a Tomcat 4.1.12 server (WinNT). Uploading form fields and files of any size from a JSP form worked perfect. Now I'm deploying the exact same webapps (thus same JSP pages and API
package) for production on another Tomcat Server (4.1.24), which this time uses a JK2 connector with an IIS Server. The upload of fields works fine. But when I try to upload files (jpg files allowed only) on this new setup, it seems that files lower than ca. 54 KB can be uploaded successfully, while files greater in size cannot be uploaded at all. I get that exception :


org.apache.commons.fileupload.FileUploadException: Processing of multipart/form-data request failed. Stream ended unexpectedly

It seems to happen while parsing the request (upload.parseRequest(request)).

I've upgraded to the latest version (fileupload 1.0 final, June 2003) : still the same error. Changing the init parameters (sizethreshold, sizemax, etc) doesn't seem to make any difference either. I've looked through the list archives and bug reports for the FileUpload API, but I cannot find any solution to this problem.

Please can you help me ? Thanks a lot.
Best regards,
Alain



**********************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager.
**********************************************************************



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to