Comments on: ColdFusion 8 : Changes with File Upload

By: Steve Stout

Steve Stout — Mon, 30 Jun 2008 21:45:00 +0000

Increasing the file upload size in the machine.config file is what ultimately fixed this problem for us.

It’s in the link http://thedotnet.com/nntp/69797/showpost.aspx as listed above.

By: Rupesh Kumar

Rupesh Kumar — Fri, 30 May 2008 12:06:00 +0000

Yes. It is indeed a bug – thanks to Chee and others for reporting . We will release a fix for this shortly. I had my setting as 10GB with which everything was working. So for the time being, you can use that as work around till you get the actual fix.

By: Chee

Chee — Fri, 02 May 2008 04:42:00 +0000

Rupesh, thanks for the response. In my ColdFusion 8 standard edition, I cannot put any number greater than 2GB in "Maximum size of post data" or else I will receive this error:

"error Posted content length of 95585 exceeds limit of -2147483648".

So, the maximum value I can put in is only 2047 MB. For the "Request Throttle Memory", if I put in more than 2047 MB, I will receive this error:

"javax.servlet.ServletException: ROOT CAUSE:
coldfusion.util.MemorySemaphore$MemoryUnavailableException: Memory required (925170494 bytes) exceeds the maximum allowed memory."

FYI, I have 2GB of physical RAM on the server. Have you seen the above errors before?

By: Rupesh Kumar

Rupesh Kumar — Wed, 30 Apr 2008 08:00:00 +0000

Chee,
In ColdFusion 8, since file upload will not keep it in the memory, you dont need a higher heap size.

Regarding other settings, you can keep all of these to be very high on your server so that file upload does not go through the throttle at all. In my local setting, I had everything to be 20 GB.

By: Rupesh Kumar

Rupesh Kumar — Wed, 30 Apr 2008 07:51:00 +0000

Thanks a lot everyone specially John H., Kim and Brian for finding out a solution for this crazy IIS problem.

By: Chee

Chee — Mon, 28 Apr 2008 04:35:00 +0000

Hi Rupesh,

When you mentioned uploaded 5GB file through ColdFusion 8, may I know what is the setting you used for "Maximum size of post data" and "Request Throttle Memory"? What is your total physical memory size in your machine?

Thanks!

By: Brian

Brian — Fri, 25 Apr 2008 13:05:00 +0000

We had the same upload problems with IIS 6 and Cf8.01 until this fix that my project lead implemented based on the posts above.

The SSLAlwaysNegoClientCert="TRUE" had to be set in a file called MetaBase.xml found in the directory C:\WINDOWS\system32\inetsrv

In order to modify this file you have to shutdown the IIS services and web sites.

Then modify the file by adding the SSLAlwaysNegoClientCert="TRUE" statement to the xml file in the section IIsWebService.

There was another SSL statement there already so he put it above that statement as he thought it needed to be in order.

Once the modifications were complete, then he restarted the services and web sites.

By: Anonymous

Anonymous — Wed, 23 Apr 2008 19:07:00 +0000

Kim,

Could you point us to the syntax of making that change using Adsutil? We'd like to give that a try.

Thanks for your post!

John H.

By: Anonymous

Anonymous — Fri, 11 Apr 2008 11:17:00 +0000

Good post… Thanks.

By: kim

kim — Thu, 03 Apr 2008 17:13:00 +0000

We worked with Microsoft to solve this problem. To summarize what we did to get this issue resolved….
We set SSLALwaysNegoClientCert property to true. We had to do this with the adsutil not metabase explorer. The readaheadsize needs to stay as the default values. We have not had any upload problems for a couple weeks and we have uploaded files as large as 100mg.