>   It seems that a no-longer-here developer had
> written a template where in
> when conditions were met, a custom tag was called,
> and an email was
> generated. He had named his custom tag the same as
> the calling template.
> Well, the conditions were finally met, and in the
> end, some poor woman got
> 116,000 emails.
>
>   So, with an example this time, is there a straight
> forward way of shutting
> this loop down? Possibly a way of setting up a
> template to do it? Someway
> other than shutting the service down? We ended up
> having to kill the service
> to stop it. We initially tried making changes to the
> template hoping to
> force it to error out...but the system had cached all
> of the pertinent
> information and was on cruise control.

One suggestion I've heard is to use ClusterCats (requires CF
Enterprise), even on 1 machine, to monitor the service and
restart it if it consumes X% CPU for X amount of time. Just a
thought...

-Ron

------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to