Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of paul.szynol@gmail.com
 designates 209.85.216.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=sender:message-id:date:from:reply-to:user-agent:mime-version:to
         :subject:references:in-reply-to:content-type
         :content-transfer-encoding;
        b=sAp56GeI9t3MZSoRA2sp3eLkuqnnEldsJ+kNQPKzo5m8PKvk4E0SDq1IPQSUfy9zNY
         IkOX1SAKJaYbAuz2UhdQnq9GtUuaJ3WhXM9eMQ/jysj9wjQQk99SLvMrV4HFyGIpWjDy
         2qioyRrUDTnRYZsVvz/SUhIY/bWjdx1sZSqds=
Sender: Paul Szynol <paul.szynol@gmail.com>
Message-ID: <4C7EDAB0.90108@columbia.edu>
Date: Wed, 01 Sep 2010 18:58:56 -0400
From: Paul Szynol <pjs38@columbia.edu>
Reply-To: pjs38@columbia.edu
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
 rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: users@tomcat.apache.org
Subject: Re: FileUploadBase$IOFileUploadException
References: <4C7EBFEA.9040801@columbia.edu>
	<4C7EC317.6030804@christopherschultz.net>	<4C7EC57E.2010504@columbia.edu>
	<4C7ECCDC.1070306@christopherschultz.net>	<4C7ED05D.2070105@columbia.edu>
	<AANLkTinfMg0_WXQPGraSu2GATO2xw41i1y=ACB=SY5NF@mail.gmail.com>
	<4C7ED587.3060406@columbia.edu>
 <AANLkTinkXEzuS9zfheCPuKC+LQgXMKhQbSsCiWSsSu6m@mail.gmail.com>
In-Reply-To: <AANLkTinkXEzuS9zfheCPuKC+LQgXMKhQbSsCiWSsSu6m@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


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<pjs38@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-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org