tracker issue : CF-3041771

select a category, or use search below
(searches all categories and all time range)
Title:

Bug 83592:Please add a new querytimeout to go with the new "query timeout" DSN setting added in CF9

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/

Reporter/Name(from Bugbase): Charlie Arehart / charlie arehart (Charlie Arehart)

Created: 07/14/2010

Components: Database, General

Versions: 9.0

Failure Type: Unspecified

Found In Build/Fixed In Build: 0000 /

Priority/Frequency: Normal / Unknown

Locale/System: English / Platforms All

Vote Count: 26

Problem:

Please add a new querytimeout to go with the new "query timeout" DSN setting added in CF9. Where the old CFQUERY TIMEOUT does not work, this new "query timeout" DSN setting does, but of course it would be very helpful to be able to do it per query.I have discussed this more in a blog entry: http://www.carehart.org/blog/client/index.cfm/2010/7/14/hidden_gem_in_cf9_admin_querytimeout/
Method:


Result:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3041771

External Customer Info:
External Company:  
External Customer Name: charlie arehart
External Customer Email: 03D0090C44723473992015D5
External Test Config: 07/14/2010

Attachments:

Comments:

This bug has been voted..
Vote by External U.
21731 | November 11, 2011 12:47:40 AM GMT
This bug has been voted..
Vote by External U.
21732 | November 11, 2011 12:47:41 AM GMT
This bug has been voted..
Vote by External U.
21733 | November 11, 2011 12:47:42 AM GMT
This bug has been voted..
Vote by External U.
21734 | November 11, 2011 12:47:44 AM GMT
This bug has been voted..
Vote by External U.
21735 | November 11, 2011 12:47:45 AM GMT
This bug has been voted..
Vote by External U.
21736 | November 11, 2011 12:47:47 AM GMT
This bug has been voted..
Vote by External U.
21737 | November 11, 2011 12:47:48 AM GMT
This bug has been voted..
Vote by External U.
21738 | November 11, 2011 12:47:49 AM GMT
This bug has been voted..
Vote by External U.
21739 | November 11, 2011 12:47:50 AM GMT
This bug has been voted..
Vote by External U.
21740 | November 11, 2011 12:47:52 AM GMT
This bug has been voted..
Vote by External U.
21741 | November 11, 2011 12:47:53 AM GMT
This is very important for me
Vote by External U.
21742 | November 11, 2011 12:47:55 AM GMT
This bug has been voted..
Vote by External U.
21743 | November 11, 2011 12:47:56 AM GMT
This bug has been voted..
Vote by External U.
21744 | November 11, 2011 12:47:58 AM GMT
This bug has been voted..
Vote by External U.
21745 | November 11, 2011 12:47:59 AM GMT
This bug has been voted..
Vote by External U.
21746 | November 11, 2011 12:48:00 AM GMT
This would be very useful if it were a per-query setting.
Vote by External U.
21747 | November 11, 2011 12:48:02 AM GMT
This bug has been voted..
Vote by External U.
21748 | November 11, 2011 12:48:03 AM GMT
This bug has been voted..
Vote by External U.
21749 | November 11, 2011 12:48:05 AM GMT
Would be extremely useful.
Vote by External U.
21750 | November 11, 2011 12:48:06 AM GMT
This bug has been voted..
Vote by External U.
21751 | November 11, 2011 12:48:08 AM GMT
+1 - and for: THIS.defaultAttributes.cfquery.queryTimeout (once we can set default attributes in Application.cfc's THIS scope)
Vote by External U.
21752 | November 11, 2011 12:48:10 AM GMT
This is definitely something that is needed.
Vote by External U.
21753 | November 11, 2011 12:48:12 AM GMT
Tested with the following code . Working perfectly fine : <cfquery datasource="oracle11g" name="x" timeout="10"> SELECT TEST_SLEEP(15) FROM DUAL </cfquery> oracle11g = datasource created after running driver.cfm (Comment added from ex-user id:gtiwari)
Comment by Adobe D.
21717 | January 25, 2012 06:31:00 AM GMT
Adobe, could you please explain what you mean by "cannot reproduce"? This is a feature request. So... err... *obviously* you can't reproduce it! -- Adam
Comment by External U.
21718 | January 22, 2014 10:09:09 AM GMT
+1 -- Adam ////////////////
Vote by External U.
21754 | January 22, 2014 10:11:09 AM GMT
Folks, following up on Adam's comment below, and in addition to all the favorable votes on the right, I'll note something I had said in the blog entry but did not say here: It's not necessary to create a new "querytimeout" attribute (for cfquery, if instead the existing "timeout" attribute could be changed to work the same (time out long queries in the same was) as does this new DSN "query timeout" setting. But if for some reason the existing attribute can't use that same logic, that's why I proposed the new one. To whoever at Adobe marked the bug as closed and cannotreproduce, could you confirm what you tried? I offered a specific example in my blog that did work differently between the two timeout features, and the votes and the comments at the blog suggest that the new DSN query timeout does indeed help with some long-running queries, where the old timeout attribute does not.
Comment by External U.
21719 | January 22, 2014 11:34:41 AM GMT
How did Gaurav think we were going to guess that was what was going on here? And how is it that he didn't bother to post back on the ticket "hey, I can't replicate this, so maybe I'm missing something: Charlie can you please elaborate?" -- Adam
Comment by External U.
21720 | January 23, 2014 01:52:32 AM GMT
Well, you are referring to the bug that was closed 2 years back. The bug was closed on Jan 25th 2012. If I remember correctly, this was just before our bugbase for Server became public and at that time in the new bug tracking system, there was no way to communicate back and the only way to reach out to the users was through mails.
Comment by Rupesh K.
21721 | January 23, 2014 04:27:49 AM GMT
Rupesh... this bug was *raised* on the public bug tracker, wasn't it? That's how it got here. THIS version of the public bug tracker has been around since at least March 2011, and there's been a public bug tracker since at least April 2010. But you know this, don't you? If you were being honest. And did Gaurav contact Charlie? I would think Charlie would have mentioned that if so. Isn't this *really* more another case of you lot not being particularly good at communicating with your clients? Because there is a strong precedent set for this after all. So Ockham's Razor kind of points to that being the more likely scenario, doesn't it? -- Adam
Comment by External U.
21722 | January 23, 2014 04:52:41 AM GMT
FWIW, I tested on MS SQL Server 2008 on ColdFusion 9, and the TIMEOUT attribute on CFQUERY seems to behave has expected (ie: how Charlie has asked for it to behave). It would be helpful it Rupesh stopped trying to have a pissing competition and instead clarified what Gaurav tested, so we can see if there's any gaps in it which might need addressing. Did he test ALL the drivers? Did he simply test one and go "yeah, works OK on my machine" and closed the ticket? Also, the ticket is marked "NeedMoreInfo"... WHAT MORE INFO do you need? It's all well and good saying you need more info, but you need to tell us what it is! -- Adam
Comment by External U.
21723 | January 23, 2014 05:00:15 AM GMT
@Adam, I don't want to go in an unending discussion on this. I don't have the exact date but this is what I remember - The public bug base was opened in March 2011 but at that time only CFBuilder was made public. The ColdFusion server bugs were migrated later and were made public in the *new* bug base around Jan-Feb 2012. This period was during the transition phase when internal migration had happened but was not opened to public. Anyways.. there is no point in going back in history and lets end that debate here.. Coming back to the bug - We are verifying this once more and since so many people have voted on this, we would appreciate if you share in which scenario this does not work.
Comment by Rupesh K.
21724 | January 23, 2014 06:23:41 AM GMT
I have verified it on ColdFusion9 and ColdFusion10 along with Oracle 11g. It works fine. "Query Timeout" DSN setting is a global setting for all the queries which are using that data source. However, "Timeout" attribute used at CFQuery level is specifically for that query only. So, it depends on the user whether they want to use timeout at the query level or data source level. However, preference will be given to the "timeout" which is defined at the query level. Please share the following details at nimsharm@adobe.com if the "timeout" attribute is not working for you at the query level: 1. Database being used. 2. Setting Summary, do not strip the data source section.
Comment by Nimit S.
21725 | February 10, 2014 03:18:26 AM GMT
I have a few queries that aren't essential that they complete, but (very rarely) run very long. I would love to be able to use a timeout attribute for just those queries that always works (ala the feature in the cfadmin).
Vote by External U.
21755 | November 04, 2014 09:53:08 AM GMT
would be good as a cfquery attribute
Vote by External U.
21756 | November 21, 2014 10:56:31 AM GMT
I believe I've confirmed this bug still exists. I've found the following: I) CF Admin's "Query Timeout (seconds)" setting behaves identically to cfquery's timeout attribute. II) CF Admin's "Query Timeout (seconds)" setting and cfquery's timeout attribute behave correctly for a MSSQL 'WAITFOR DELAY' query. III) CF Admin's "Query Timeout (seconds)" setting and cfquery's timeout attribute behave incorrectly for a MSSQL SELECT * query against a 2gig table having ~1.5 million rows 1) Create a 2gig MSSQL table named "myTable" having 1.5 millions rows 2) In CF's Admin, create a Microsoft SQL Server DSN "myDSN" for myTable w/ Query Timeout of 20 seconds. Leave all other advanced settings at their defaults. 3) Run <cfquery name="q" datasource="myDSN" result="r" timeout="10">WAITFOR DELAY '00:01'</cfquery> 4) In 10 seconds, see "[Macromedia][SQLServer JDBC Driver]Execution timeout expired." thrown (good). 5) Run <cfquery name="q" datasource="myDSN" result="r">WAITFOR DELAY '00:01'</cfquery> 6) In 20 seconds, see "[Macromedia][SQLServer JDBC Driver]Execution timeout expired." thrown (good). 7) Run <cfquery name="q" datasource="myDSN" result="r" timeout="10">SELECT * FROM myTable</cfquery> 8) In 60 seconds, where 60 is the request's timeout, see "The request has exceeded the allowable time limit Tag: CFQUERY" thrown (bad). 9) Run <cfquery name="q" datasource="myDSN" result="r">SELECT * FROM myTable</cfquery> 10) In 60 seconds, where 60 is the request's timeout, see "The request has exceeded the allowable time limit Tag: CFQUERY" thrown (bad). Verified in CF11u5 w/ MSSQL 2012 on Windows 2012 R2. Thanks!, -Aaron
Comment by External U.
21726 | July 22, 2015 05:30:58 PM GMT
Hi Nimit, I've also sent you an email. Thanks!, -Aaron
Comment by External U.
21727 | July 22, 2015 05:59:52 PM GMT
Wow, this has been closed with the reason "notabug"? I didn't file it as a bug report. I filed it as a *feature request*. It says so clearly at the top: "Feature CF-3041771" Adobe, why are you closing feature requests with that status?
Comment by External U.
21728 | July 22, 2015 07:37:01 PM GMT
Hi Charlie, I communicated w/ Nimit via email on July 22-23. I provided a repro case clearly showing cfquery's timeout attribute was ignored. I just now saw your comment indicating that this ticket was closed as NotABug on the 23rd. I thought the issue was still being worked on, b/c I'd never heard any further communication from Adobe. Adobe, can you please tell us why it is NotABug for cfquery's timeout attribute to be ignored? Thanks!, -Aaron
Comment by External U.
21729 | September 30, 2015 02:58:00 AM GMT
"was closed as NotABug on the 23rd" should've been "was closed as NotABug on the 22nd"
Comment by External U.
21730 | September 30, 2015 02:58:40 AM GMT