ColdFusion中onError与cferror同时使用的异常问题排查

Let’s work through your problem step by step, since both the onError method and <cferror> tag are giving you headaches:

Core Problem Recap #

• Your onError method used to reliably catch errors and redirect users to error.cfm, but now it only returns a generic 500 status code.
• Swapping to <cferror> broke your data entry forms entirely—they won’t even load.
• Re-creating the Application.cfc hasn’t fixed the issue, and your manager made changes to this file recently.

First: Fix the cferror Form Loading Failure #

When you enabled <cferror>, it’s likely catching every single exception (including minor, harmless ones like empty queries or undefined variables that were previously being suppressed). These trivial errors are triggering the error template before your form can finish rendering.

Quick Fix for cferror #

Narrow down which exceptions <cferror> handles to only critical, fatal types:

<!--- Only catch high-severity exceptions, not minor ones --->
<cferror template="error.cfm" type="exception" exception="application, database, template, expression, missinginclude" mailTo="Generic@org.edu" />

This way, trivial errors won’t hijack your form loading process.

Next: Restore & Repair the onError Method #

Your commented-out onError has a couple of subtle issues that could be causing it to fail silently:

1. Output Restriction Conflict #

Your method has output="no", but you’re using <cfmail> with <cfoutput> and <cfdump>. While ColdFusion usually tolerates this, output restrictions can sometimes interfere with error handler execution. Remove output="no" to eliminate this conflict.

2. cflocation Isn’t Reliable in onError #

In some ColdFusion versions, <cflocation> inside onError can fail (especially if the error occurs early in the request lifecycle). Instead, use <cfinclude> to serve the error template directly—it’s more consistent.

Revised onError Method #

<!--- Uncomment this and remove the cferror tag --->
<cffunction name="onError" access="public" returntype="void">
    <cfargument name="exception" required="yes">
    <cfargument name="eventname" type="string" required="yes">

    <!--- Send error details via email --->
    <cfmail from="QDP@org.edu" to="Generic@org.edu" subject="Quality Data Portal Error Encountered" type="html">
        <cfoutput>
            The following error was encountered on #dateformat(now(), 'dddd mmmm dd, yyyy')# at #timeformat(now(), 'hh:mm:ss tt')#<br /><br />
            <cfdump var="#arguments.exception#">
            <cftry><cfdump var="#arguments#"><cfcatch></cfcatch></cftry>
            <cfdump var="#form#">
            <cfdump var="#session#">
            <cfdump var="#cgi#">
        </cfoutput>
    </cfmail>

    <!--- Serve error template directly instead of redirecting --->
    <cfinclude template="error.cfm">
    <cfabort>
</cffunction>

3. Check ColdFusion Administrator Settings #

Your manager might have changed global settings that override your Application.cfc logic:

• Go to Server Settings > Settings and ensure Enable Robust Exception Information is disabled (this can bypass custom error handling in production).
• Check Error Handling > Exceptions to confirm no global exception handlers are prioritized over your onError method.
• Disable Trusted Cache temporarily if you’re testing changes (cached versions of Application.cfc can prevent updates from taking effect).

4. Verify Application Initialization #

Make sure onApplicationStart is running correctly by adding a log statement:

<cffunction name="onApplicationStart" access="public" returntype="boolean" output="no">
    <cfset application.dataSource = 'quality' />
    <!--- Log to confirm app initialization --->
    <cflog file="AppInit" text="QualityDataPortal started successfully" type="Information">
    <cfreturn true />
</cffunction>

Check your ColdFusion logs (usually in {CF_INSTALL}/logs/) to confirm the app is initializing properly.

Final Testing Steps #

1. Remove the <cferror> tag and uncomment your revised onError method.
2. Restart the application (rename Application.cfc temporarily, then rename it back, or use the CF Administrator to restart the app).
3. Trigger a deliberate error (e.g., an invalid database query or undefined variable) to confirm error.cfm loads and the error email is sent.

内容的提问来源于stack exchange，提问作者Andrew