Just getting back to this thread. I've only seen this issue before when you upgrade M2 and don't restart the server.
Do you per chance have multiple versions of this app running on this same server with the *same* cf app name? IIRC, the app specific mappings are on a per app basis. If you have two apps with the same name starting up at the same time - they will share the same app scope and mappings. However it appears that you have a version of M2 in each app context and there AppLoader is on two different places on the disk. There is a possible threading issue (race condition) if two apps are starting at the same time with the same MachII.* mapping paths. That could be why it is complaining that the AppLoader isn't the correct AppLoader. Check on that and let me know On Feb 28, 2011 10:13 AM, "Jacob" <[email protected]> wrote: -- Come see Team Mach-II at OpenCFSummit - Feb 21-23, Dallas, TX - http://www.opencfsummit.org/ To post to this group, send email to [email protected] For more options and to unsubscribe, visit this group at http://groups.google.com/group/mach-ii-for-coldfusion?hl=en SVN: http://svn.mach-ii.com/machii/ Wiki / Documentation / Tickets: http://trac.mach-ii.com/machii/
