CFMX7's numerous "request has exceeded the allowabletime limit Tag" bomboffs

[WebManWlkg]

Prior to CFMX, you could bump up the RequestTimout on the URL, example:
mypage.cfm?RequestTimeout=120. Under CFMX (6.1) you could do it with cfset
Variables.RequestTimeout = 120 (from Ben Forta, and that always seems to work)
or reputedly by cfsetting (from the documentation, and I say reputedly because
I don't know anyone who's ever gotten that way to work).

Now, under CFMX7, I'm seeing "request has exceeded the allowable time limit
Tag: (((tagname)))" EVERYWHERE. Just for fun, go to Google and search for
"request has exceeded the allowable time limit" (with the double quotes).
You'll find page after page after page of ColdFusion pages that crashed while
the Google spider was indexing them. I find it difficult to believe that
suddenly so many people don't know how to set the RequestTimeout.

Have the rules for changing RequestTimeout changed AGAIN in CFMX7? Does
cfsetting finally work now, and they took away setting Variables.RequestTimeout
without telling anyone??? Or is there something else going on besides the
request timeout?

[WebManWlkg]

I just wrote a little test program that loops millions of times (doing nothing
else) and takes 67.316 seconds to complete. I set the request timeout in CF
Admin to 60 seconds. I tried setting Variables.RequestTimeout to 120 and
crashed with "request has exceeded the allowable time limit". I tried again
with cfsetting RequestTimeout="120" and that works now.

So the answer is, if you're running CFMX 6.1 and can't seem to get cfsetting
requestTimeOut to work, try Ben Forta's method of setting
Variables.RequestTimeout instead. But remember, when you upgrade to CFMX 7,
you'll have to convert over to using the documented way, because it now works
in CFMX 7, and Variables.RequestTimeout doesn't.

I feel sorry for everyone who used Ben Forta's undocumented feature because
they couldn't get the documented unfeature to work.