As our company has just moved into using persisting components across our clusters, we ran into the same issue. We decided to use a properties file to "version" our packages. On preprocess, if the version number for the package differs from the one in the application's scope, we reload the persisting components of that package. We don't use the J2EE server version of CFMX, but I'm sure a similar process would work in that instance. We also use this technique to reset the frameworks just so we can avoid having to use internal ips, ports, etc., as our setup has over 100 applications running on a server at one time or another. We also limit code pushes affecting the components to once a week, others twice a week. It helps cut down on these types of issues. HTH,
Phil -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas Knudsen Sent: Tuesday, May 02, 2006 8:33 AM To: [email protected] Subject: Re: [Reactor For CF] reactor and J2EE clusters Doug, sorry, its not a 100% Reactor issue, just saw this bit of code in the samples <!--- If the ReactorFactory hasn't already been loaded then load it ---> <cfif NOT IsDefined("Application.Reactor") or IsDefined("url.reset")> <cfset Application.Reactor = CreateObject("Component", "reactor.reactorFactory").init(expandPath("/ReactorSamples/ContactManage r/reactor.xml")) /> </cfif> and I wondered how folks fared using this in clusters, SW ones. I like Jared's suggestion! Sean, I envy your setup there. We host about 20 internal apps and the business is ALWAYS changing processes and such, so we have many updates. Luckily I've laid down the law so to speak and limit production changes to twice a week. Folks screamed about it, but things are more stable. I've learned that if you have a process that allows frequent and immediate updates to production code, we developers certainly are lazy and end up testing code in production, eh? anyhoo...enough of this thread back to reactor goodness. thanks. Doug On 5/2/06, Doug Hughes <[EMAIL PROTECTED]> wrote: > This may not really be a reactor issue, but I'd be interested in knowing the > answer :) > > Doug > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Douglas Knudsen > Sent: Monday, May 01, 2006 9:46 PM > To: [email protected] > Subject: Re: [Reactor For CF] reactor and J2EE clusters > > updating what is cached. If code caches a instance of CFC a in say > the application scope, then a changes due to a update, how to get the > new version cached elegantly? Currently we have J2EE clusters setup. > We use IIS, hitting ourdomain.com/appname/?reset=yes obviously doesn't > work. I have the internal JRun servers turned on and I have to hit > each internal JRun server instance with something like > ourdomain.com:8300/appname/?reset=yes for each internal port number. > I have yet to find any elegant type approach to do this. Has > adobe.com some slick trick to do this? Maybe I just have to stick it > out, eh? I'm not griping, just wondering if there is a purty slick > way to do this. > > > Hope this made some sense...I'm in 'shock and awe' after my intro to > Reactor today...simply amazing. > > DK > > On 5/1/06, Sean Corfield <[EMAIL PROTECTED]> wrote: > > On 5/1/06, Douglas Knudsen <[EMAIL PROTECTED]> wrote: > > > anyone using reactor and J2EE clustering? I've always found using > > > cached cfcs with these type of SW clusters to be a real PITA when it > > > comes to refreshing the cache. Anyone doing this have any input? > > > > adobe.com uses J2EE clustering and a lot of cached CFCs without > > problems - perhaps you can explain what you find to be troublesome > > about your usage so that we can better understand what the perceived > > problem is? > > -- > > Sean A Corfield -- http://corfield.org/ > > Got frameworks? > > > > "If you're not annoying somebody, you're not really alive." > > -- Margaret Atwood > > > > > > > > -- Reactor for ColdFusion Mailing List -- [email protected] > > -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/ > > > > > > > > > -- > Douglas Knudsen > http://www.cubicleman.com > this is my signature, like it? > > > > -- Reactor for ColdFusion Mailing List -- [email protected] > -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/ > > > > > > -- Reactor for ColdFusion Mailing List -- [email protected] > -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/ > > > -- Douglas Knudsen http://www.cubicleman.com this is my signature, like it? -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/ -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
