Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 7226 invoked from network); 3 Oct 2006 14:33:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 Oct 2006 14:33:12 -0000 Received: (qmail 98760 invoked by uid 500); 3 Oct 2006 14:33:07 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 98637 invoked by uid 500); 3 Oct 2006 14:33:07 -0000 Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Users List" Reply-To: "Jakarta Commons Users List" Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 98626 invoked by uid 99); 3 Oct 2006 14:33:07 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Oct 2006 07:33:07 -0700 X-ASF-Spam-Status: No, hits=0.3 required=5.0 tests=MAILTO_TO_SPAM_ADDR Received: from [128.240.234.65] ([128.240.234.65:42923] helo=cheviot3.ncl.ac.uk) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id 66/90-08153-D9472254 for ; Tue, 03 Oct 2006 07:33:03 -0700 Received: from moonraker.campus.ncl.ac.uk (moonraker.ncl.ac.uk [10.8.234.171]) by cheviot3.ncl.ac.uk (8.13.6/8.13.1) with ESMTP id k93EWj7X002924 for ; Tue, 3 Oct 2006 15:32:45 +0100 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: RE: [fielupload] how much big size file can be handled? Date: Tue, 3 Oct 2006 15:32:45 +0100 Message-ID: <2ED602334F87F94CB1CA268F9608C19402D6E8F1@moonraker.campus.ncl.ac.uk> In-Reply-To: <20061003105247.14471.qmail@web58301.mail.re3.yahoo.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [fielupload] how much big size file can be handled? Thread-Index: Acbm3g2tzptL4iYERjq+eGLBoCHwxQAGpKHQ From: "Arijit Mukherjee" To: "Jakarta Commons Users List" Received-SPF: pass (cheviot3.ncl.ac.uk: 10.8.234.171 is authenticated by a trusted mechanism) X-Newcastle-MailScanner-Information: Please contact Postmaster@newcastle.ac.uk for more information X-Newcastle-MailScanner: Found to be clean X-Newcastle-MailScanner-MCPCheck: MCP-Clean, MCP-Checker (score=0, required 1) X-Newcastle-MailScanner-From: nam48@cpx.ncl.ac.uk X-NCL-Spam-Status: No X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I've been able to upload files almost upto 2GB. I'm stuck at files > 2GB, and I suspect it's because of the native O/S and not a commons fileupload problem. Cheers Arijit=20 >-----Original Message----- >From: Leena Kulkarni [mailto:leenakulkarni2003@yahoo.com]=20 >Sent: 03 October 2006 11:53 >To: commons-user@jakarta.apache.org >Subject: [fielupload] how much big size file can be handled? > > Hi Friends, > >I have few questions about the commons file upload. > >1) Is commons file upload suitable for uploading >files>10MB in size? >What we have observed that commons file upload load a file in=20 >memory. So for files > 10MB the deply in response is too much. >Is this right? Is there something we are missing? >Is there any other good variation of commons file upload if we=20 >have to use it for uploads upto 30MB? > >2)When we try uploading a file>40MB, we are getting Items list as 0. >So there is nothing to iterate on and check if it is a file. > >Code is like the following: >// Create a new file upload handler >ServletFileUpload upload =3D new >ServletFileUpload(factory); >=20 >// Parse the request >List /* FileItem */ items =3D >upload.parseRequest(request); =20 >=20 >// Process the uploaded items >Iterator iter =3D items.iterator(); >while (iter.hasNext()) { > FileItem item =3D (FileItem) iter.next(); >=20 > if (item.isFormField()) { > processFormField(item); > } else { > processUploadedFile(item); > } >} > >We trapped this scenario and added code to show some=20 >customized error when Items are 0. But then it takes agaes to=20 >display the error message on screen when from the logs we can=20 >make out that the control did go till the point of displaying=20 >the error message to screen. > >Do not know why this behaviour for large files [>40MB]. It can=20 >be good to know the some threshold at which such error occurs=20 >and if it is a known problem with commons fileupload. > >Regards, > >__________________________________________________ >Do You Yahoo!? >Tired of spam? Yahoo! Mail has the best spam protection=20 >around http://mail.yahoo.com=20 > >--------------------------------------------------------------------- >To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org >For additional commands, e-mail: commons-user-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org