tracker issue : CF-3148695

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

cflocation triggers Quartz exception

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/NotABug

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 03/25/2012

Components: Scheduler

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Public Beta /

Priority/Frequency: Major / Some users will encounter

Locale/System: English / Win All

Vote Count: 0

If a task's handler call encounters a location/cflocation, then a Quartz exception is thrown.

(code attached)

Steps:
1) Load index.cfm?browser (so redirect only occurs for handler call)
2) See this in exception.log

"Error","DefaultQuartzScheduler_QuartzSchedulerThread","03/23/12","06:18:22",,""coldfusion.runtime.AbortException"

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

Watson Bug ID:	3148695

External Customer Info:
External Company:  
External Customer Name: itisdesign
External Customer Email:

Attachments:

  1. March 25, 2012 00:00:00: 1_CFLocationBreaksTaskHandlerCall.zip

Comments:

Related thread: http://prerelease.adobe.com/r/?3c9667225d6841e5b4fde29578aa48d7
Comment by External U.
19970 | March 25, 2012 01:36:02 AM GMT
From your post on another thread, i get an impression that you have an IIS Virtual Host configured. Can you please check if this works fine when you put this application somewhere under webroot?
Comment by Himavanth R.
19971 | March 26, 2012 03:53:01 AM GMT
Hi Himavanth, Yes, I was using IIS sites. So, I just now copied those 3 files directly into C:\inetpub\wwwroot and ensured eventhandler="MyCFC", and loaded http://localhost/?browser Yes, same coldfusion.runtime.AbortException is also logged in this scenario. Thanks, -Aaron
Comment by External U.
19972 | March 26, 2012 05:04:36 AM GMT
IIS7.5 on 64-bit Windows 7 (in case that helps)
Comment by External U.
19973 | March 26, 2012 05:05:37 AM GMT
cflocation always throws an abortexception since it aborts the request. The error is handled internally and sends appropriate header in the response to perform client side redirect. In the case of task event handlers, since there it is no HTTP request, cflocation does not actually mean anything and therefore the error is as expected.
Comment by Rupesh K.
19974 | April 02, 2012 07:33:18 AM GMT
Hi Himavanth and Rupesh, The issue arose b/c event handler requests used to invoke Application.cfc methods. If an Application.cfc method contained cflocation, then the event handler request was interrupted. Now event handler calls ignore Application.cfc methods, so no more issue. Thanks!, -Aaron
Comment by External U.
19975 | May 28, 2012 11:32:16 PM GMT