To set the record straight: ColdFusion 4.5.1 SP2 (specifically) was the only version of ColdFusion to get hung on zero-byte mail written to the spool. The file handle of the mail would get written and ColdFusion would encounter some other runtime error that caused the leaked file handle to be completed. The secondary effect of this is that CF would get stuck sending out or moving the bad mail file and race the cpu. 1 cpu would spike to 99-100%, and 2 cpu would spike at exactly 50% each.... flat line.
That exact bug was fixed in ColdFusion 5, but unfortunately a very similar bug was discovered in CF5. In that version mail files would get written with just 1 or 2 characters in them and nothing else. The reason for the bad mail was very likely the same... another type of runtime error would cause CF to not complete the mail file. In CF5, the secondary effect was to spike the cpu in an irregular manner where the cpu util would range from 60-100 % up and down, not flat lined as was CF4.5.1SP2. The solution for each of the above was to look for all "unknown exception" and pcode errors in the logs and fix them, as well as fixing any runtime error occurring on pages involving the CFMAIL tag. After a brief review of this thread, I suggest looking at the size of [cfhome]/registry/cf.registry. It should be about 15 - 20 Kilobytes. I suspect that the size of this file might be significantly larger, perhaps 250 KB to 1MB or more. If so, then client variables are likely being stored in the registry and the best solution would be to remove them from the registry and stop the practice of storing them there. The symptoms of this problem begin as general slowdowns in performance, and later as cpu spiking and constant crashing and coring. See also: 1) Tuning the ColdFusion Administrator http://www.defusion.com/articles/index.cfm?ArticleID=130 2) Managing Client Variables http://www.macromedia.com/v1/cfdocs/administering_coldfusion_server/03_configuring_coldfusion_server/admin036.htm 3) Enabling External Client State Management http://www.macromedia.com/v1/cfdocs/administering_coldfusion_server/03_configuring_coldfusion_server/admin038.htm 4) ColdFusion 4.5.1 SP2 and Up: Recommended Settings for Client Variable Storage http://www.macromedia.com/v1/handlers/index.cfm?ID=21170&Method=Full 5) Deleting Client Variables Stored in the Registry http://www.macromedia.com/v1/handlers/index.cfm?ID=20340&Method=Full -Steven Erat Macromedia -----Original Message----- From: mark s [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2003 5:16 PM To: CF-Linux Subject: CF5 on RH 7.2 running very unreliably Thanks Dave I guess this is worth trying - I've had a guy on cfaussie post a similar solution. However, restarting the cfserver on a heavily session based app is not really ideal. I guess it beats having it restarting every 30 seconds. I have also chatted to a cf developer here in oz about managing session manually rather than relying on the session scope. Maybe these two solutions in conjunction are the answer. Maybe another option is to can CFMAIL and go with some alternative. Any suggestions on what to use? Many Thanks Mark ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=14 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=14 This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.14
