I’m having two weird issues with my Coldbox app. At some point in time, I start receiving random errors that all seem to stem for the application “forgetting” how it’s configured. When I reinitialize my application, everything works again.
I have several modules that are enabled and some log box functionality configured. The two issues I see are: 1) it seems to forget that I have one of the modules loaded and 2) it seems to forget that I have log box correctly configured.
Neither of the errors have any direct relationship to a specific request or handler… Luis, I have full stack traces for these errors that I can send you directly if you would like more contextual info.
Here are the two error messages:
Message Error including config file: Error loading module routes as the module requested ‘aqmd’ is not loaded. The loaded modules are:
Message Element ROOT is undefined in a CFML structure referenced as part of an expression.
Anyone have any thoughts about why these are happening?
Currently module-reload is turned off… I do currently have config auto reload on though… while I understand there are some performance implications, I wouldn’t expect having reloading enabled to introduce problems.
“production” for us is also a dev platform at the moment. Since we have some differences between our live and test environments (things that are unavoidable at the moment), we are constantly tweaking some code in our production environment. Once we reach a more stable point (in a week or so), we will be reconfiguring the app to re-enable caching and turn off any of the auto-reloading. The volume of traffic on this application is extremely low, so performance is a secondary priority at the moment.
Please check that you ColdFusion Administrator > Caching > Component Cache is “not checked”.
Ben in all sincerity. Config auto relad is a setting that is extremely dangerous in production as it treats the incoming request as the first request. So multi threaded capabilities are limited and contention errors will arise. I would recommend turning it off.
3.5 also dropped this setting entirely.
I have already disabled it and will let you know if the problems I was seeming persist.