This content has been marked as final. Show 5 replies
60 seconds is the default Page timeout. If your queries are taking longer than 60 seconds, then you have a problem. You need to add indexes to the DB or you are loading too much data/too many records.
To get around this timeout, you can append the variable RequestTimeout to the page link as in
where 300 is the number of seconds or in your page, add:
<cfsetting RequestTimeout = "300">
Hope that helps.
I've already tried that. It does not seem to take it into account.
To get around this timeout, you can append the variable RequestTimeout
to the page link as in MyQuerypage.cfm?RequestTimeout=300 where 300 is
the number of seconds or in your page, add: <cfsetting RequestTimeout =
I just want to clarify that the ?RequestTimeout=xxx option has be
deprecated in the latest versions of CF in favor of the <cfsetting
requestTimeout = xxx> option. So, unless you are using an older version
of CF, you should use the latter option.
> After exactly 60 seconds I get an error of type: "Page cannot be
> displayed"....I have researched this type of error and cannot find anything
Is this in IE? You might want to switch off "friendly error messages" to
see if it gives you anything better.
I'd also break down your code to find out which bit is causing the timeout.
Jeez. That's an interesting schema you've got there. It doesn't *look*
very normalised. Is it? Could it be (more ~)?
> <cfloop query="getRec">
How many records is this likely to be?
> After exactly 60 seconds I get an error of type: "Page cannot be displayed"
"Exactly 60 seconds" most likely means that, in the Coldfusion Administrator, Server Settings => Settings => Timeout Requests after(seconds) is configured to 60. Delete all the timeout attributes, for example, in cfquery tags, clear the caches in the Coldfusion Administrator and set the request timeout to an appropriate value.
> I have tried adding the default cfadmin timeout to e.g. 180 to no avail.
Did you press the button to Submit Changes? Restart Coldfusion to refresh everything? As a last, nay, desperate, measure, you could edit the system file C:\CFusionMX7\lib\neo-rumtime.xml. Set the value of timeoutRequestTimeLimit to 180.0