I hate to say it but most errors are code-related. One thing to do is to log long-running templates. Set the warning indicator down to lets say 5 seconds and see what happens then. Anything taking 5000 ms+ to run should be examined closely.
Terminate long-running requests. Once you figure out about how long your longest-running template should be running, set the termination value to a number safely less more than that, but not inordinately more. One way to regain stability (at the expense of performance) is to choke down the number of simultaneous threads you allow. Minimum reasonable number is one thread per processor but be very careful not to kill off your ability to process your traffic. Set the CF server to restart at one hung thread less than your maximum number of allowed threads. This will give you the opportunity to let CF restart itself when it knows it has a problem. Fix whatever error that was thats getting flagged. It may not be as harmless as you think. Just some thoughts. Bughunts are certainly no fun -- --mattRobertson-- Janitor, MSB Web Systems mysecretbase.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:209486 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
