From user-return-22626-apmail-commons-user-archive=commons.apache.org@commons.apache.org Wed Mar 04 12:40:34 2009 Return-Path: Delivered-To: apmail-commons-user-archive@www.apache.org Received: (qmail 37013 invoked from network); 4 Mar 2009 12:40:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Mar 2009 12:40:33 -0000 Received: (qmail 84832 invoked by uid 500); 4 Mar 2009 12:40:29 -0000 Delivered-To: apmail-commons-user-archive@commons.apache.org Received: (qmail 84763 invoked by uid 500); 4 Mar 2009 12:40:28 -0000 Mailing-List: contact user-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Users List" Delivered-To: mailing list user@commons.apache.org Received: (qmail 84752 invoked by uid 99); 4 Mar 2009 12:40:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Mar 2009 04:40:28 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of wardlootens@gmail.com designates 64.233.182.184 as permitted sender) Received: from [64.233.182.184] (HELO nf-out-0910.google.com) (64.233.182.184) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Mar 2009 12:40:20 +0000 Received: by nf-out-0910.google.com with SMTP id e27so386415nfd.30 for ; Wed, 04 Mar 2009 04:39:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=52EU9cSMh8VuCY427+QAyMFPf9E/XMydUkPX2XOhRvo=; b=cWobvQwPqmB8q9ZWaDR09SNeJF8igd1W8pSkDu75FTCTr7X/DOTTmV+nrlBWaoAcN8 y6GKVf3EtvfiOmq6tLbvHF/sdcyKrybtwhJ2/w2G7CvNbRQXffp/9rBtAiBuktBBxsvL fDHvh2cZmmsDfO05M6L/mvpG4YULXrZkfxbmk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=K73sBg0cu5FLMF8GJkcVrsePwO2nlV4BsTcCSEOHoc2J0C0NZCmNPtcZz0v2aO+O5H aHE75GDUww5XNVR/suurbngrP9U7kJVQ4o9GwjGOkm0XlW8koWHCXNm2+AJeQKHWk2Pk qO/+Tc4rFIGSHTGLvlpqE8MDhySw2CHw3aPFQ= Received: by 10.216.12.67 with SMTP id 45mr623599wey.218.1236170399374; Wed, 04 Mar 2009 04:39:59 -0800 (PST) Received: from ?192.168.0.136? (d54C2B68D.access.telenet.be [84.194.182.141]) by mx.google.com with ESMTPS id h7sm413229nfh.12.2009.03.04.04.39.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 04 Mar 2009 04:39:59 -0800 (PST) Message-ID: <49AE76A2.6070302@gmail.com> Date: Wed, 04 Mar 2009 13:40:02 +0100 From: Ward User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Commons Users List Subject: Re: [FILEUPLOAD] Problem with huge files (>2GB) References: <49AE713F.3010600@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi I didn't set an file upload limit, so it uses the default (which is unlimitted, and not 2GB) I'm using a Tomcat serer, but I don't think the problem lies there... (I set maxPostSize on 0 which means unlimited) Grtz Ward Raghuveer.V schreef: > I understand you have a problem of file upload size limit. > Check the docs if it has defult size of 2 GGB. > I used upload which is with struts. > In struts which uses commons-upload ,the upload size can be controlled > in struts-config.xml file > > Let us see if some one suggests a alternative solution. > > > > ----- Original Message ----- From: "Ward" > To: > Sent: Wednesday, March 04, 2009 5:47 PM > Subject: [FILEUPLOAD] Problem with huge files (>2GB) > > >> Hello, >> >> I'm currently working on a web application which sould be able to deal >> with large multimedia-files. >> For uploading the files I'm using the Apache Commons FileUpload library. >> This works great for files up to 2GB, but when I try it with files >> larger than 2GB, things go wrong: >> The upload doesn't start, in fact, the doPost()-method of the Servlet >> which handles the upload-request is never called. >> >> I think this might have something to do with the contentLength-property >> of ServletRequest, which is an integer (so contentLengths > 2GB would >> cause an overflow), but I'm not sure this is the problem. >> >> So: is it true that the maximum size of a post to a servlet cannot >> exceed 2GB? >> And is there somenone who could giveme some hints about how to make it >> possible to upload huge files? Files-sizes up to 50GB and more should be >> supported (raw and un-encode videofiles that are) >> >> Thanks in advance, you would really help me out! >> >> Grtz >> >> Ward (Belgium) >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org >> For additional commands, e-mail: user-help@commons.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@commons.apache.org > For additional commands, e-mail: user-help@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@commons.apache.org For additional commands, e-mail: user-help@commons.apache.org