On Friday, January 27, 2012 10:21:44 PM UTC+11, Stephen M wrote:
I've replicated this problem on my local workstation using a network db
server, so its no longer about Amazon.
I can get the timeout error on the stored proc as below. But the problem
is I am getting this timeout at the 120 sec mark when the CF Request
timeout, the datasource query tiomeout and the IIS connection timeouts are
all set to 300 secs or more.
A stupid question - does the query timeout in the datascource setting apply
to stored procs as well? I assume that it would.
I also notice that on my dev server I have some extra settings under
Request Tuning that I don't have on the win 2008 servers which are only CF9
standard. The extra settings are for Request Queue Timeout settings. I
have increased that to the same as the regular request timeout because it
says
"If a request has waited in the queue for this long, timeout the request.
This value should be at least as long as the Request Timeout setting
(currently 300 seconds)."
The next setting is for a Request Queue Timeout page
"Specify a relative path from the web root to an HTML page to send to
clients when a template request times out before running, for example
/CFIDE/timeout.html. The page you specify cannot contain CFML. If you do
not specify a page, clients receive a 500 Request Timeout error when their
request does not run. "
This immediately attracts my attention because it is the first time I have
seen the mention of the 500 Request Timeout error which is what I get if I
do not set Enable HTTP status codes.
Changing the Request Queue Timeout hasn't made any difference and I don't
have that setting on the server anyway but I'm curious as to what effect it
actually has. The real timeout (as timed by me with my watch) is 120 secs,
so I was wondering if the request waiting after the stored proc in the
queue is the one triggering the timeout error. As in, the stored proc
finally comes back after 2 minutes, then CF looks at the next request in
the queue and says that CFLOOP has been there too long so its timed out.
But in that case the Request Queue timeout setting should fix it but it
hasn't. I'll try a reboot and run it again.
=================
15:33:20.020 - Application Exception - in
C:\WorkingDirectory\RTE\wwwroot\trunk\RTEreports\com\roymorgan\RTEreports\services\ReportDAO.cfc
: line 83
The request has exceeded the allowable time limit Tag: CFSTOREDPROC
--
You received this message because you are subscribed to the Google Groups
"cfaussie" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/cfaussie/-/cJmIKCjsQcsJ.
To post to this group, send email to cfaussie@googlegroups.com.
To unsubscribe from this group, send email to
cfaussie+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/cfaussie?hl=en.
