Paul, I have exactly the same problem. You are not alone. Here's an additional dimension of the cfftp problem. I back up some files of various sizes to a remote site using an automated cf task. The page essentially loops through an array of files that it determines need to be ftp'd (backed up). In the loop is the cfftp tag and attributes to put the file. [Note that I discovered (through some back and forth with the Adobe team) that a "dummy" connection name is *required* for the timeout variable to be effective.]
In the looped cfftp tag, I set the timeout attribute for each putFile action dynamically, allowing 15 secs per MB of filesize, with a minimum of 31 seconds per file. "small" files ftp just fine. The first "big" file ftp attempt completes just fine (i.e., the file transfer is complete), but then CF seems to lose its place. The evidence for this is that not a single line of code is executed after the big file transfer...the page simply dies (although it says 'done'). I've tried everything [or so it seems]. I've set the cfsetting requesttimeout to 3600 (60 minutes). No effect. I've tried setting up and using a cfftp connection with a 3600 timeout. The connection gets killed after the first reuse of the connection. Any suggestions welcome! I use "small" and "big" here in quotes only because I haven't iterated enough to find the dividing line. 60MB and up files definitely cause the problem and 2MB files don't cause the problem. LMK if you've discovered any work arounds to this very annoying problem. > Hi All, > > It's been a long time since I've had to use CFFTP (CF5) so I may well > be missing something but I seem to have come across a couple of things > one of which, I consider to be a bug. > > Firstly, the bug. > > I need to download a large (600Mb) file, if I set the timeout value to > something like 5 seconds for my connection then the tag times out > after 5 seconds rather than after 5 seconds of inactivity. There is a > major difference here. > > If I set the timeout to 30 seconds, I get about 45Mb down before the > tag times out. > If I set the timeout to 300 seconds, I get about 450Mb down before the > tag times out. > > If I set the timeout to something silly, say 120000 seconds, the tag > just hangs (I assume until the timeout is reached). (I know why this > is). > > If I set the timeout to something more reasonable, say 900 seconds, > the tag does not return until the 900 seconds are up and I get the > file :-). > > CFFTP is hanging until timeout because of the config of the FTP server > (something I cannot change as it's a 3rd party server). I've double > checked the connection with standard FTP clients and they too hang at > the end until their timeout is reached. > > The difference between CFFTP and other FTP clients is that other FTP > clients can have timeouts of say 5 seconds and only timeout after the > entire file has been downloaded. Ideally this is what CFFTP should do > and I'd consider it to be a bug if it did otherwise which it does. > > Secondly, the annoying problem. > > The server I'm connecting to requires a PASV connection from where I > am. Ideally, I would like set this on the first connection and have CF > track this in the connection structure that is created. It isn't. > Every CFFTP call I make, I have to set passive="Yes". Until I dumped > out the connection structure, I couldn't figure out why I wasn't even > able to list a set of directories after the initial connection as I'd > assumed that passive being an attribute of the connection would be > carried through in the connection struct. This is not so. Annoying, > fixable but shouldn't be there. > > Paul > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;203748912;27390454;j Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:307475 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
