tracker issue : CF-3963559

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

this.timeout in Application.cfc is not properly setting the request timeout

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): Bryce Holycross / Bryce Holycross (Bryce Holycross)

Created: 04/01/2015

Components: Language, CF Component

Versions: 11.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: CF11_Final / 11,0,11,301867 , 2016.0.0.298074

Priority/Frequency: Normal / Unknown

Locale/System: English / Windows 7 64-bit

Vote Count: 2

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_fixed on July 06, 2016 using build 2016.0.01.298513
Problem Description:
this.timeout in Application.cfc is not properly setting the request timeout

Steps to Reproduce:
1.  CFAdmin setting: Timeout Requests after 30 seconds
2.  <cfset this.timeout = 50 /> in Application.cfc
3.  Run Index.cfm with the following code:
<cfset startTickCount = getTickCount() />
<cfset sleep(35000) />
<cfset endTickCount = getTickCount() />
<cfset seconds = (endTickCount - startTickCount)/1000 />

Actual Result:
A timeout occurs

Expected Result:
I should see "35" on the screen
With <cfsetting requesttimeout="50" /> in onRequestStart() in the Application.cfc I see "35" as expected when running Index.cfm

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

Watson Bug ID:	3963559

External Customer Info:
External Company:  
External Customer Name: Bryce
External Customer Email:  
External Test Config: My Hardware and Environment details:


  1. June 21, 2016 00:00:00:


upgrading to CF11 breaks long-running requests in our application
Vote by External U.
7956 | April 02, 2015 09:21:40 AM GMT
the upgrade to CF11 is breaking longer running processes.
Vote by External U.
7957 | April 02, 2015 09:45:17 AM GMT
Fix verified on Build: 295672 Test case used as attached in the bug.
Comment by Kailash B.
7945 | September 23, 2015 04:03:42 AM GMT
Hi Adobe, I see this is Closed/Fixed. What CF11 build is this fixed in? Thanks!, -Aaron
Comment by External U.
7946 | January 04, 2016 08:32:41 PM GMT
The issue seems to still be here in cf11u8, any news about this?
Comment by External U.
7947 | June 13, 2016 06:55:17 PM GMT
This bug has been marked as fixed but seems to still occur on cf11u9. I've uploaded a sample project using the code in the bug's steps-to-reproduce. Can someone give me feedback in this? This is pretty crippling since the workaround doesn't work in the context of an ajax request.
Comment by External U.
7948 | June 20, 2016 09:19:58 PM GMT
Hi Adobe, There is confusion here? Did you fix this for CF11 or only in CF2016? "Fixed In Build" shows empty. Customers are reporting this is still an issue in CF11. I could look into this, but first want to confirm which version(s) this was fixed in. Thanks!, -Aaron
Comment by External U.
7949 | July 05, 2016 01:47:17 PM GMT
For reference, I opened bug #CF-4168693 to follow-up (still unanswered as of now).
Comment by External U.
7950 | July 05, 2016 05:48:07 PM GMT
Hi all, I've confirmed the issue is fixed in CF2016 but not CF11 (as of CF11 Update 7 build 11,0,07,296330). Adobe: This really should be fixed for CF11. It was filed April 1, 2015. Thanks!, -Aaron
Comment by External U.
7951 | July 06, 2016 12:27:04 PM GMT
Comment by Aaron N.
7952 | July 27, 2017 06:52:31 AM GMT
Adobe's comment from CF-4168693: ---- We will see if this fix can be back-ported to 11.0. We will track this bug via CF-3963559, hence, closing this as a duplicate. Comment by Vamseekrishna Nanneboina 08/03/2016 03:23:14 GMT ---- That was nearly 1 year ago. THIS.timeout doesn't work in CF11. It needs to. Is Adobe still tracking this issue?? Thanks!, -Aaron
Comment by Aaron N.
7953 | July 27, 2017 06:57:05 AM GMT
Hi Aaron, This bug was fixed in CF 11 Update 11. I have updated the fixed in build information. Thanks, Suchika
Comment by Suchika S.
7954 | July 27, 2017 09:20:33 AM GMT
Hi Suchika, Thanks very much for confirming (and updating the build info)! -Aaron
Comment by Aaron N.
7955 | September 30, 2017 08:35:44 PM GMT