Comments on: How is this timeout on CFLOOP possible? http://blog.crankybit.com/how-is-this-timeout-on-cfloop-possible/ Take a byte out of tech! Wed, 08 Feb 2012 15:54:01 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Josh http://blog.crankybit.com/how-is-this-timeout-on-cfloop-possible/#comment-10246 Josh Sun, 16 Dec 2007 05:27:58 +0000 http://blog.crankybit.com/how-is-this-timeout-on-cfloop-possible/#comment-10246 Mike, this was on a CFMX 7 server. I wouldn't be surprised if this behavior has been around since CFMX 6, though. I would seriously look into the possibility of a timeout from a related function, like Dan suggested. I highly suspect this was the issue for my situation. Mike, this was on a CFMX 7 server. I wouldn’t be surprised if this behavior has been around since CFMX 6, though. I would seriously look into the possibility of a timeout from a related function, like Dan suggested. I highly suspect this was the issue for my situation.

]]> By: Mike http://blog.crankybit.com/how-is-this-timeout-on-cfloop-possible/#comment-10215 Mike Sat, 15 Dec 2007 13:28:54 +0000 http://blog.crankybit.com/how-is-this-timeout-on-cfloop-possible/#comment-10215 What version of Coldfusion server are you running? I have the same problem with coldfusion 8, same code ran fine on coldfusion 5, now it is timing out on cfdirectory... What version of Coldfusion server are you running? I have the same problem with coldfusion 8, same code ran fine on coldfusion 5, now it is timing out on cfdirectory…

]]> By: Josh http://blog.crankybit.com/how-is-this-timeout-on-cfloop-possible/#comment-4673 Josh Thu, 27 Sep 2007 21:21:42 +0000 http://blog.crankybit.com/how-is-this-timeout-on-cfloop-possible/#comment-4673 Wow. Seven years of developing in CF and I've never seen a situation where that was the apparent answer. Of course, I've spent most of that developing apps for a server that I control. Thanks for that insight. It's still weird that CFDIRECTORY would timeout. One time it will execute in less than a second, then next time it times out. And naturally, the hosting company refuses to lift a finger. I swear I must be the only CF customer on this server. Wow. Seven years of developing in CF and I’ve never seen a situation where that was the apparent answer. Of course, I’ve spent most of that developing apps for a server that I control. Thanks for that insight.

It’s still weird that CFDIRECTORY would timeout. One time it will execute in less than a second, then next time it times out. And naturally, the hosting company refuses to lift a finger. I swear I must be the only CF customer on this server.

]]> By: Dan G. Switzer, II http://blog.crankybit.com/how-is-this-timeout-on-cfloop-possible/#comment-4627 Dan G. Switzer, II Wed, 26 Sep 2007 21:10:34 +0000 http://blog.crankybit.com/how-is-this-timeout-on-cfloop-possible/#comment-4627 The timeout messages in CF can be misleading. I suspect it's actually timing out on the CFDIRECTORY line (which is probably because a file is in use and it's causing issues with reading the files.) The reason the message can sometimes be misleading is because CF won't actually timeout after XX seconds on some operations (such as a CFQUERY operation.) It actually has to complete the full operation first. So if you have a query that takes 60 seconds to run, but your template timeout is set to 30 seconds the query won't just stop after 30 seconds. It'll run the entire query first and then throw an error (so the error would occur after 60 seconds, not 30 seconds.) Also, since that operation completes, the error that is reported as "timing out" is actually the next line that gets executed. That's why I suspect it's actually the CFDIRECTORY tag that's causing the timeout. The timeout messages in CF can be misleading. I suspect it’s actually timing out on the CFDIRECTORY line (which is probably because a file is in use and it’s causing issues with reading the files.)

The reason the message can sometimes be misleading is because CF won’t actually timeout after XX seconds on some operations (such as a CFQUERY operation.) It actually has to complete the full operation first.

So if you have a query that takes 60 seconds to run, but your template timeout is set to 30 seconds the query won’t just stop after 30 seconds. It’ll run the entire query first and then throw an error (so the error would occur after 60 seconds, not 30 seconds.)

Also, since that operation completes, the error that is reported as “timing out” is actually the next line that gets executed.

That’s why I suspect it’s actually the CFDIRECTORY tag that’s causing the timeout.

]]>