TechNote (Archived)

ColdFusion MX: ReservedTemplateException

When reviewing your Macromedia ColdFusion MX exception log, you may come across a "ReservedTemplateException" entry. The Java stack trace for the exception will display the following:

 coldfusion.filter.ApplicationFilter$ReservedTemplateException:     at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:72)    at coldfusion.filter.PathFilter.invoke(PathFilter.java:80)    at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:47)    at coldfusion.filter.BrowserDebugFilter.invoke(BrowserDebugFilter.java:52)    at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28)    at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:35)    at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:43)    at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)    at coldfusion.CfmServlet.service(CfmServlet.java:105)    ...

The exact stack trace may vary slightly depending on the edition of ColdFusion MX that you are running, such as the Server configuration or the J2EE configuration with different J2EE servers.

This exception is thrown when ColdFusion receives requests from a client for Application.cfm or OnRequestEnd.cfm. These templates are special templates reserved by ColdFusion for configuring application level settings. They cannot be directly executed by a client. Any direct request for these reserved templates are considered illegal requests and will trigger the exception.

If you infrequently see the exception in the log file, it may be that some user has mistyped the request. It is a good idea to make sure no other template names resemble Application.cfm or OnRequestEnd.cfm. If it appears more frequently, you may want to determine who is requesting these templates and why. However, in any case, you may safely ignore the exception since ColdFusion MX will properly protect access to these templates.