Re: [Mach-II] Persistent Behavior with Mach-ii/ColdSpring

2011-03-17 Thread Peter J. Farrell
Jeffrey Battershall said the following on 03/17/2011 12:37 PM: > Re: MACHII_APP_KEY, only about 50% of the 11 sub apps > have MACHII_APP_KEY defined. If you multiple M2 applications sharing the same CFML application memory space, the MACHII_APP_KEY needs to be unique for each of your applications.

Re: [Mach-II] Persistent Behavior with Mach-ii/ColdSpring

2011-03-17 Thread Kurt Wiersma
Are you using the Mach II provided ColdSpring property in all your Mach II apps? If so can you post the configuration you are using? --Kurt On Thu, Mar 17, 2011 at 12:37 PM, Jeffrey Battershall wrote: > Peter, > Re: MACHII_APP_KEY, only about 50% of the 11 sub apps have MACHII_APP_KEY > defined.

Re: [Mach-II] Persistent Behavior with Mach-ii/ColdSpring

2011-03-17 Thread Jeffrey Battershall
Peter, Re: MACHII_APP_KEY, only about 50% of the 11 sub apps have MACHII_APP_KEY defined. re: CS version: 1.2 Re: accessing CS, application.serviceFactory.getBean('ConfigBean') ia typical. Jeff On Thu, Mar 17, 2011 at 11:42 AM, Peter Farrell wrote: > Are you setting the MACHII_APP_KEY differ

Re: [Mach-II] Persistent Behavior with Mach-ii/ColdSpring

2011-03-17 Thread Peter Farrell
Are you setting the MACHII_APP_KEY differently for each M2 app that is sharing the same cfml app memory space? How are you accessing ColdSpring (calling getBean() in each request)? What version of CS? On Mar 17, 2011 10:13 AM, "Jeffrey Battershall" wrote: > Dave, > > Just to clarify, we aren't r

Re: [Mach-II] Persistent Behavior with Mach-ii/ColdSpring

2011-03-17 Thread Dave Shuck
If you are naming them the same, they are essentially the same application, so your assertion about one monolithic app is indeed correct. I would not be surprised if you have found what you thought were inconsistencies with OnServerStart() start as well, since whichever Mach-II application was hit

Re: [Mach-II] Persistent Behavior with Mach-ii/ColdSpring

2011-03-17 Thread Jeffrey Battershall
Dave, Just to clarify, we aren't running just one application - each separate Mach-ii app has its own Application.cfc. That said, the fact that the applications are NAMED the same might have the same effect has one monolithic app. The overwrite scenario certainly sounds like that we're looking at

Re: [Mach-II] Persistent Behavior with Mach-ii/ColdSpring

2011-03-17 Thread Dave Shuck
I don't endorse the approach of running multiple Mach-II applications under a single application for this very type of reason, although I work at a company that did this very thing well before I came aboard! I think the quickest workaround would be to at least have your applications point to a sin

Re: [Mach-II] Persistent Behavior with Mach-ii/ColdSpring

2011-03-17 Thread Jeffrey Battershall
Thanks Dave, Yes, we're running multiple ColdSpring factory instances, and yes, it does sound like what you're describing. The question is how to circumvent the behavior. Any ideas? Jeff On Thu, Mar 17, 2011 at 10:37 AM, Dave Shuck wrote: > So, just to be clear, these are separate Mach-II app

Re: [Mach-II] Persistent Behavior with Mach-ii/ColdSpring

2011-03-17 Thread Dave Shuck
So, just to be clear, these are separate Mach-II applications (not modules, or includes) that are all under the same Application? I would imagine that if that is the case, you probably have a mechanism to load ColdSpring in each of those applications, and if that is indeed the case, I suppose it p

[Mach-II] Persistent Behavior with Mach-ii/ColdSpring

2011-03-17 Thread Jeff B
Hi, We're using Mach-ii 1.6.1 in production (CF9) and have an architecture with a root application and many sub applications, and many of these are using ColdSpring. These sub apps are all named the same in Application.cfc to facilitate session-sharing across applications. One in particular is al