There have been fixes for >2GB size uploads and downloads between June 10 and June 5. If we assume, that those fixes will help, you've got a coupe of options:

- try with Tomcat 6.0.14, which already contains the fixes. This is a major update, but since you are already using Java 5+, you shoujld be able to do it in much less than a day.

- we plan to tag a new 5.5 release very soon (end of the week or shortly after). If the tag looks good, you can expect a new 5.5 release in around 2-4 weeks. A 5.5.25 tarball will be available earlier (likely first half of next week), so you can already test it, although it will not be officially released at that time.

- You can build your own 5.5 from the sources in the publicly available source code management system subversion.

Of course we don't know, if there will be more problems related to libs and the platform with the big uploads and downloads, but at least we checked, that Tomcat itself handles the Content-Length headers correctly with the above mentioned fixes.

In case you additionally combine Tomcat with Apache HTTPD or IIS via mod_jk/isapi redirector: the same problem (handling large file contents) has been fixed there recently. This is included in release 1.2.24 of this web server plugin.

Regards,

Rainer

David Hesson wrote:
Completely sorry, details follows:

System:
Windows XP (Home I believe) 32 bit
2GB Memory on my system

Web Application Details/ Other Details:
JSF Framework (1.1?)
Commons File Uploads 1.2 attempted to be used
Tomcat 5.5.17
I'm going to say that Sun is my JVM vendor??
JVM is version 1.6
Tomcat is using these settings: -Xms512m -Xmx512m (I am not receiving PermGens/OutOfMemoryExceptions by any means)

I'm compiling at a source level of 1.6 for the web application, the JVM vendor is SUN

I do have somewhat of a clue as to why the upload itself is not functional when just trying to use the Commons File Upload to stream the file to a temporary location when large uploads are detected. The content-length has a maximum value of 2.x billion, which is right under two gigabytes. A 2.xGB file will result in a negative content length from integer overflow into the final, negative bit position. Other than that, I cannot explain why the servlet/.jsp target of the form post is not being hit and the filter chain calls filters over and over but won't go any further. After pressing submit, the page acts like nothing happened, and no error messages are generated. I'm fresh out of college so my lack of experience/knowing what you meant by JVM level kind of threw me off, I have JRE1.6 and JDK1.6 :(

Here is what came out in Command Prompt issuing this command:

 >java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode)

Thanks once again

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to