Ben Nadel
On User Experience (UX) Design, JavaScript, ColdFusion, Node.js, Life, and Love.
Ben Nadel at cf.Objective() 2014 (Bloomington, MN) with: Jeff McDowell and Joel Hill and Jonathan Rowny and Shawn Grigson and Jonathan Dowdle and Matt Vickers and Christian Ready and Asher Snyder and Clark Valberg and Oscar Arevalo and David Bainbridge and Josh Siok
Ben Nadel at cf.Objective() 2014 (Bloomington, MN) with: Jeff McDowell@jeff_s_mcdowell ) , Joel Hill@Jiggidyuo ) , Jonathan Rowny@jrowny ) , Shawn Grigson@shawngrig ) , Jonathan Dowdle@jdowdle ) , Matt Vickers@envex ) , Christian Ready@christianready ) , Asher Snyder@ashyboy ) , Clark Valberg@clarkvalberg ) , Oscar Arevalo@oarevalo ) , David Bainbridge ( @redwhitepine ) , and Josh Siok@siok )

ColdFusion Runtime Abort Exception

By Ben Nadel on
Tags: ColdFusion

I keep getting emails when my site errors. I like to be alerted; however, I kept getting an email when I went to fiew any files. The kink was, the file was working. Went to it, saw it, all was good. And yet, still the emails. Upon further investigation, it seems the error being thrown was an AbortException. After two seconds of Google time, I see that Raymond Camden post a solution explaining that when you use the onError event in the Application.cfc, every single CFLocation tag will throw this error. Check out his solution, its a great fix.

I had to go and change the way my arguments were coming into the onError method. Before, I was just grabbing ARGUMENTS, but now, I have to sepparate them out to reference then as above:

<!--- Store the passed arguments. --->
<cfargument name="Exception" type="any" required="true" />
<cfargument name="EventName" type="string" required="true" />

Tweet This Provocative thoughts by @BenNadel - ColdFusion Runtime Abort Exception Thanks my man — you rock the party that rocks the body!

Looking For A New Job?

100% of job board revenue is donated to Kiva. Loans that change livesFind out more »

Reader Comments