OK, we have (finally) solved our error and I thought I would share the
lesson we learned with the group. The underlying problem was being masked by
CF restarting by itself. We had Restart when requests terminate abnormally
turned on, but when we turned it off the true error started showing up:
The standard answer is to lock all your Client/Session Application
variables.
Another solution that worked for me when this happened was to uninstall CF
and reinstall it and the service packs. Rebooting between of course.
A couple of places to look are in the admin. Check the box next to log
unresponsive request longer than n minutes and you can increase or decrease
as needed until you start getting some log entries. Another place to look is
in the undeliverable mail spool, if you have any 0 byte files it will hang
