What I mean is that if your JVM runs out of memory, ColdFusion will no longer process any requests - this could happen at 200mb of a 300mb file or it could happen at 298mb.
If it's all on the same network could you not use UNC paths? That would be even quicker and would not require a thread to be tied up - you could also use some Async ColdFusion. Your heap size may or may not be enough - it all depends on your application. You could take it to 2GB if you have 6GB on the machine. The rest will be used by the OS. "This e-mail is from Reed Exhibitions (Oriel House, 26 The Quadrant, Richmond, Surrey, TW9 1DL, United Kingdom), a division of Reed Business, Registered in England, Number 678540. It contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you have received this communication in error please return it to the sender or call our switchboard on +44 (0) 20 89107910. The opinions expressed within this communication are not necessarily those expressed by Reed Exhibitions." Visit our website at http://www.reedexpo.com -----Original Message----- From: Mik Muller <[EMAIL PROTECTED]> To: CF-Server <[email protected]> Sent: Mon Dec 05 15:53:21 2005 Subject: Re: using java class files >a theoretical limit is possible but that is down to available RAM etc. Well, that's a limit, isn't it? What happens when we try to upload a very large file is after about 300 mb we get the following error: 500 null And it's not a time-out thing. I tested this by logging in via Remote Desktop and uploading an 800 mb file which took under a minute (as you'd expect). So maybe it's an IIS thing? I have the CF JVM Heap Size set to 1024, if that matters. What other configs can I change? Is there a way to have the file(s) spool straight to the hard drive instead of to memory (which seems a little silly if you ask me). Better yet, to a particular HD and folder? I know, I know. Several people have said I'm crazy for trying to accept very large files via HTTP, but we want to integrate the upload into the application. FTP moves us out of the application and adds a bunch of security and synchronization issues. Plus, the people who want to do these very large uploads will be doing so over an internal network (University) so the uploads won't take very long. Michael At 05:40 AM 12/5/2005, James Holmes wrote: >Another possibility that might be artificially imposing what looks >like a limit might be the request timeout setting in the CF Admin. >It's worth checking to see if this setting is enabled. > >On 12/5/05, Robertson-Ravo, Neil (RX) ><[EMAIL PROTECTED]> wrote: > > Michael > > > > As noted previously - there is **no** limit uploading a file via CFFILE - a > > theoretical limit is possible but that is down to available RAM etc. > >-- >CFAJAX docs and other useful articles: >http://jr-holmes.coldfusionjournal.com/ > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:10:5726 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/10 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:10 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.10 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
