As I have already written on this blog we are huge fans of the FuseBox framework. Our application (which will be released in private beta testing soon) is build with FuseBox 5.x.
Lately we have run into a couple of "…is undefined in a CFML structure referenced as part of an expression…" error messages. After hours of trying to figure out what the problem is, we figured we try to search the net (as humble a we are we are always thinking it is our fault…).
After a couple of minutes, we found that others had these errors as well and have posted the "workaround". It seams that this is due to a race condition and there are two options to "fix" this:
- Switch your application to "production" mode. The application.fusebox structure won't be rebuilt every request this way, and concurrent requests will no longer be affected.
- Put an exclusive application-scoped lock around the include to the runtime in index.cfm, while the application is in development mode. This will force concurrent requests into a single thread and each request should safely be completed before the next one begins.
Both of the above workaround work and solved our "problems".
If you enjoyed this post, make sure you subscribe to the RSS feed!
Add your comment below, or trackback from your own site.
Subscribe to these comments.
Be nice. Keep it clean. Stay on topic. No spam.
You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>