Paul Szynol
Wed, 01 Sep 2010 15:59:27 -0700
Ah, now I see what you mean. So the reason the exception isn't being thrown when I increase the threshold value is that the image isn't being written to disk in the first place. That makes more sense. But the odd part of it (in my configuration, at least) is that the file permissions do allow fileupload to write the file...so, I guess I still don't understand what's causing the exception.
On 9/1/10 6:52 PM, Konstantin Kolinko wrote:
2010/9/2 Paul Szynol<pj...@columbia.edu>:Hey, Konstantin, The file system allows me to write the bigger image if I just increase the threshold size, though, so the file system is allowing the larger images. That suggests to me that the exception is being thrown solely when the image size exceeds the threshold size value. I read the exception to mean something like "I can't write this tmp file because it is bigger than the threshold size value", rather than "I can't write this tmp file because the file system won't let me".http://commons.apache.org/fileupload/apidocs/org/apache/commons/fileupload/disk/DiskFileItemFactory.html#setSizeThreshold%28int%29 I understand that if you use setSizeThreshold() to increase the threshold value, the file is not written to disk:On 9/1/2010 5:28 PM, Paul Szynol wrote:Increasing the value of .setSizeThreshold() did the trick. Thanks for pointing me in that direction--I should have sent my question here about 12 hrs ago! :)Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org