I never like to contradict Mr Wilson, but an unnamed application becomes part of the global application, which is shared server wide. Try this an you'll see a whole bunch of fun things
*Application.cfm* <cfapplication> <cfif !structKeyExists(application, "test")> <cfset application.test = now() /> </cfif> <cfdump var="#application#" /> You'll notice that application.test will not change on each request. This doesn't mean that your issue is unrelated, but i just wanted to clarify what the behaviour was (on ACF, dunno about Railo/OBD) imho an Application.cfm with nothing but <cfabort /> in it is totally safe, any template that invokes it will simply abort execution so it should not be able to cause a timeout. I use them in my views and config directories and have never had a problem, as the Application.cfm file is not executed when the file is read or <cfinclude>'d. If the template that handles communication with your CAS system is invoking an Application.cfm with a <cfabort> in it, it should never work... Chris On 12 April 2011 22:09, Brian Swartzfager <[email protected]> wrote: > > > I've seen this happen when the application name was not set in > application.cfm/c > > > > With no name, the application is created anew each request. > > ...As much as I hate to admit it (because that means I did something > stupid), you may have hit the nail on the head there. I have > Application.cfm files containing just cfabort in certain directories > in my app to defeat any attempts to browse/view the XML files, and > while those Application.cfm files are probably okay (a user wouldn't > hit them unless they tried to browse there) there's one that resides > in the same directory as the .cfm file that handles the communication > between the app and our CAS authentication system. So the MG requests > are all part of the "appName" application scope, but the requests > involving that .cfm file are not. > > I've removed that rogue Application.cfm file: that may well be the > end of it. > > > --Brian > > -- > Model-Glue Sites: > Home Page: http://www.model-glue.com > Documentation: http://docs.model-glue.com > Bug Tracker: http://bugs.model-glue.com > Blog: http://www.model-glue.com/blog > > You received this message because you are subscribed to the Google > Groups "model-glue" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/model-glue?hl=en > -- Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog You received this message because you are subscribed to the Google Groups "model-glue" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/model-glue?hl=en
