thx wil.
The multiple instances will not really do the trick without
some planning. For example if you have appA shared/ balanced accros
instance X and Y, and appA relies on WebService Z going off
somewhere else and this is hanging, then both instance X and Y will
go down. The only viable solution I can think of is to have parts
of the appA split into basic stuff that can timeout correctly on
instance X and stuff that doesn't obey timeouts on instance Y and
use a scripty thing to determine if a user useing appA can actually
do the cool stuff on instance Y (perhaps displaying messages like
"service unavailable" or something). but this seems like a lot of
work for something that should be simple. Remember, CF is supposed
to be RAD.
The Thread killing stuff is a nightmare, as far as I can see
it always will knock over the server.
I looked at Fusion Reactor before, but never got it, just
checked out their site, they have a nice debugging thing coming out
soon.