Anyone? Bueller? I really need an answer to this -- even though I'm running
Fusion Reactor and can keep a survival strategy, this is no way to keep a
server running. Is there anyone out there who's successfully used the TIMEOUT
parameter in CFQUERY with CFMX 7.0.2 and SQL 2005 Standard?
On Tue, Apr 14, 2009 at 5:25 PM, Sung Woo s...@cornell.edu wrote:
Hi Casey,
What happened today is that the SQL server basically locked up. CF kept
waiting for the request to come back, but it never did because it just hung
infinitely. It seems as if CF waits forever in a case like this,
[mailto:s...@cornell.edu]
Sent: Wednesday, April 15, 2009 7:58 AM
To: cf-talk
Subject: Re: CFQUERY Timeout for SQL2005 Fails
Anyone? Bueller? I really need an answer to this -- even though I'm
running Fusion Reactor and can keep a survival strategy, this is no way to
keep a server running
This is an interesting thread, I've seen what I believe to be very similar
behaviour here on one of my webservices, seemed that one particular query
sometimes just hangs indefinitly, however other threads and requests are all
just fine.
I tried playing around with application request
Mark and Casey,
Thanks for clarifying this for me. I don't own the SQL Server that I need to
hit, so it looks like I'm between a rock and a hard place.
I still don't think the TIMEOUT parameter is working, though. In my example,
I'm hitting a database that is fully operational, and I have a
Also -- this may just be me being dense, but I don't get why the TIMEOUT
feature in CFQUERY has to work this way. It's CF that's making the initial
request to the datasource, so it should start counting down from the moment it
creates that request. And then after waiting for a predetermined
Hi Mark,
To answer your question -- there's a DDL transaction that's running on the
server, and from what the folks have told me, an ALTER TABLE command was
causing the lock to occur. And the downside is that giving hints (i.e., WITH
(NOLOCK)) is not going to have an effect in this
-talk
Subject: Re: CFQUERY Timeout for SQL2005 Fails
Hi Mark,
To answer your question -- there's a DDL transaction that's running on the
server, and from what the folks have told me, an ALTER TABLE command was
causing the lock to occur. And the downside is that giving hints (i.e.,
WITH (NOLOCK
The docs say, no, it may not timeout at 1 second. Check out the
livedocs... Because the timeout attribute only affects the maximum
time for each suboperation of a query, the cumulative time may exceed
its value.
And, even then, the query stuff is considered to be 3rd party (or at
least, so
Check this out. This one, as I've said before, outputs a number around 3000.
cfquery name=test datasource=dsn timeout=1
select top 2 *
from table/cfquery
cfoutput#cfquery.ExecutionTime#/cfoutput
However, this one results in an error: Error Executing Database Query.
Here's my test:
cfquery name=test datasource=dsn timeout=1
select top 2 *
from table
/cfquery
cfoutput#cfquery.ExecutionTime#/cfoutput
I'm getting 3000+ for this value. This shouldn't be, right? Because I have
the timeout parameter set for a second? The driver I'm using
Actually, I was wrong -- even cfsetting requesttimeout=1
enablecfoutputonly=No doesn't work, because it still waits for the cfquery
to finish before it outputs the timeout error. Is there any solution for this?
The database we're relying on is unstable and we need to be able to kill the
how about adding WITH (NOLOCK)
If your queries are just selecting data, i'd use WITH (NOLOCK)
that way you don't need to wait for transactions to finish if that table
gets heavy inserts
cfquery name=test datasource=dsn timeout=1
select top 2 * WITH (NOLOCK)
from table
Hi Casey,
What happened today is that the SQL server basically locked up. CF kept
waiting for the request to come back, but it never did because it just hung
infinititely. It seems as if CF waits forever in a case like this, so it's
vital that I can kill the connection from the CFQUERY.
14 matches
Mail list logo
