I just hope it is fixed in CF5. By applying file size check, does that prevent data loss. One of the big problems I've had with that bug is there is no way to recover the data the zero byte file was supposed to contain. Assuming that's an important message from a client, that data loss is unacceptable. Just placing some "if zero byte, then delete" logic dosn't really solve that problem. Besides, the spooler dosn't have any error correction on it. Malformatted e-mail will crash the spooler and spike the processor (contrary to the CF5 release notes).
I'm glad you posted this. I spoke with MM support endlessly about this. Their suggestion -> upgrade to a zero release. No, thank you. EC -----Original Message----- From: Rick Osborne [Mojo] [mailto:[EMAIL PROTECTED]] Sent: Monday, October 29, 2001 2:17 PM To: CF-Talk Subject: RE: CFmail Recount Tom muck said: > Unfortunately, ColdFusion doesn't give us the option to split the > spool directory into mulitple directories, so the server will > automatically write all the spool files out to that directory up to > 65,535 files before crapping out. Then it only sifts through them at > the rate of 400 per minute. We had a similar problem and got around it by making our code smart enough to only spool mail if there is less than 200 files in the spool directory. Otherwise, it waits a minute and tries again. Sure, you may not be getting optimal efficiency out of your mail spool, but you're also not crashing the server. :) One caveat, tho. There is a known bug in CF4.x (fixed in CF5) that will occasionally create a zero-byte file in the mail spool. Upon trying to read this file, your cf server will go down *hard*. If you bring up the server again without deleting the file, it will just crash again. I talked to Allaire support about it last week at DevCon and they admitted that they hadn't been able to even figure out what was causing it, much less provide a permanent fix for it. They've worked around it in CF5 by doing a size test against each file before it is read, but they are *not* planning on retro-ing the fix back to 4.x. Their advice was to write a daemon in something other than CF that periodically checked the spool file for zero-byte files and deleted them. Also check to see if your CF server has already crashed and restart it. That's a bit out of the range of the majority of their customers, but that was their solution. -R Rick Osborne Certified Advanced ColdFusion 5 Developer ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
