tracker issue : CF-4204865

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

CFComponent extends path is caching

| View in Tracker

Status/Resolution/Reason: To Fix//BugVerified

Reporter/Name(from Bugbase): Michael T. / ()

Created: 07/15/2019

Components: CFComponent

Versions: 2018

Failure Type: Incorrectly functioning

Found In Build/Fixed In Build: ColdFusion 2018 Update 4 /

Priority/Frequency: Normal / All users will encounter

Locale/System: English / Win All

Vote Count: 2

The extends attribute path of the CFComponent seems to be caching on the server level the first request being made. Instead of just creating an error for the requested application, every application that uses dot notation extending the same path fails.

The error message returned is:

"The .test.componentC ColdFusion component or interface name, used to extend or implement the test.componentA component is invalid. Ensure that the file exists, that the name does not start or end with a period (.), and the name is not an empty string."

The issues occurs after installing CF2018 Update 4, seems to be related to the fix https://tracker.adobe.com/#/view/CF-4204108

Attachments:

Comments:

Using the attached file, load the URLs in the following order: (generates error) http://127.0.0.1:8500/test/component.cfm?fo=A http://127.0.0.1:8500/test/component.cfm?fo=B Clear the template cache, then load (error is resolved): http://127.0.0.1:8500/test/component.cfm?fo=B http://127.0.0.1:8500/test/component.cfm?fo=A Clear the template cache, then load the following order (error is still resolved) : http://127.0.0.1:8500/test/component.cfm?fo=A http://127.0.0.1:8500/test/component.cfm?fo=B Now restart CF, then load the following order (generates error): http://127.0.0.1:8500/test/component.cfm?fo=A http://127.0.0.1:8500/test/component.cfm?fo=B If ?fo=B is loaded first after the CF server has restarted, the error is never encountered. It seems that the template path for the extends attribute is being cached on the server level. This is CRITICAL issue because it crashes every application on the server that extends the same cfc.
Comment by Michael T.
31026 | July 15, 2019 03:00:33 PM GMT