Here is something suggested before that *may* help - Think it was bought up by David.
<form action="#CGI.SCRIPT_NAME#?#CGI.QUERY_STRING#" method="post" enctype="multipart/form-data" name="fileForm"> the curent verison has action = "" On Thu, 16 Sep 2004 12:04:37 -0400, Jeff Coughlin <[EMAIL PROTECTED]> wrote: > I'm not sure if this will help, but a few years ago a client of mine was > having difficulties with CFFILE after prolonged use of CF (I don't > recall the error, it was before CFMX). The only fix at the time seemed > to be a restart of CF Services. > > In the end we found a few problems: > 1. Memory leaks (CF needs ram to use CFFILE). > 2. Server patches (Windows, CF, and third party programs). > 3. More ram (we weren't meeting server specifications). > > Read on if still interested... > > ==================== > We next researched server utilization through tools like Windows Task > Manager. The processor was largly being consumed by CF. Long story > short... It turned out to be the way CF was handing uploads. Apparently > as you're uploading a file (or multiple files) CF loads it into ram > until it is finished with it. This of course was not good because the > javascript code we had couldn't help to restict large file sizes until > after the huge uplaod completed and rested in CF's ram (but thats > another story). > > Due to some memory leaks (either in Windows or in that version of CF -- > I think it was v4.01 at the time) the problem took a while to happen. > We patched the server (both Windows and CF) and added more ram (we were > really too low anyway at 256MB. We went to 1GB which was expensive at > the time). Fortunately for us this solved the problem (for the time being). > > As much as I don't want to say "throw money at something", you do have > to consider what your needs are and verify you are meeting them (ex. > Ram). Server patches never hurt either. > > Now here's the kicker. Six months later the problem re-occured. They > were going to brush it off as a fluke and reboot the server, however > luckily someone called my office. At the time we were lucky enough to > have a great engineer who discovered the source of the problem was not > in CF (although it did need the extra memory), but a third party program > with a memory leak. Due to the memory leak CF eventually ran out of > enough ram to accept it's file. The cleint moved the program to another > server and the problem never occured again. What they did with the > program after that I have no clue nor care :) > > Hope this is helpful, > > -Jeff > > > > --- > You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] > To unsubscribe send a blank email to [EMAIL PROTECTED] > Aussie Macromedia Developers: http://lists.daemon.com.au/ > --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
