I see the following stack trace show up a decent amount on my CF9 servers:
at java.io.WinNTFileSystem.getLastModifiedTime(Native Method)
at java.io.File.lastModified(File.java:826)
at coldfusion.compiler.NeoTranslator.getLastModifiedTime(NeoTranslator.java:990)
at coldfusion.runtime.TemplateClassLoader.getLastModifiedTime(TemplateClassLoader.java:297)
at coldfusion.runtime.InterfaceTemplateProxyCache.getTemplateProxyFromPath(InterfaceTemplateProxyCache.java:119)
at coldfusion.runtime.TemplateProxy.implementedInterfacesChanged(TemplateProxy.java:1472)
at coldfusion.runtime.TemplateProxy.verifyInterfacesImpl(TemplateProxy.java:862)
at coldfusion.runtime.CfJspPage._invoke(CfJspPage.java:2297)
at cfNoScope2ecfc1959964350$funcGETFROMSCOPE.runFunction(D:\websites\wwwroot\common\coldbox\system\ioc\scopes\NoScope.cfc:33)
Basically from what I can tell, any time CF creates an instance of a CFC that implements an interface, it confirms that it is correctly implementing it. That much is fine-- my issue is that I have trusted cache turned on, yet it is hitting the file system, presumably to check and make sure the interface cfc hasn’t changed.
I don’t have a CF10 box to test this on right now, so my questions are thus:
- Has anyone else ever noticed this?
- If so, is it resolved in CF10?
And to be clear, I don’t consider this a ColdBox bug-- though I have considered taking out all the implements=’’ in the framework just because a large about of transients being created can spend a noticeable amount of time reading the file system to check interfaces.
Thanks!
~Brad
ColdBox Platform Evangelist
Ortus Solutions, Corp
E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com