I actually have session sharing off now, using sticky sessions. Yeah, it was pretty kewl when I had it enabled. The issue we had was with the charting engine and we had one app where the developer stored CFCs in the session scope. The charting engine will not work with session sharing on and sticky sessions off. You can work around it by using the NAME attribute of the chart tag and cffile I suppose, but we had no resources to change the code around here. Either way, its really a neato thing to have setup. Now, if I was only lucky enought to have CF7 now....long story....setting up an instance and cluster is point and click easy in CF7. DK
On 6/22/05, jacksonj @ calib. com jacksonj @ calib. com <[EMAIL PROTECTED]> wrote: > > >by CFMX cluster you are speaking of SOFTWARE based clustering in JRun, > not a > >load balancer correct? Try this code below, it will tell you what > instance > >you are on. I use this. Its a real PITA though to make sure you are on > >instance foo or goo. > > > > > ><cfobject action="create" type="java" class="jrunx.kernel.JRun" name="jr" > /> > ><cfset servername = jr.getServerName() /> > ><p><cfoutput>JRun Server Name: #servername#</cfoutput></p > > Yes, I'm currently using that code to tell me *which* machine I'm actually > updating; However I just have to keep hitting the page until I have > eventually hit both Machine A and Machine B (it's luck of the draw, since I > can *know* which machine I'm on, but I can't *specify* which machine to be > on). This is obviously not ideal, but is my current, temporary workaround. > > >Now, another solution, one I am getting ready to use: In my JRun cluster, > I > >have the internal webserver turned on for each instance. You need to do > this > >anyway to get at the CFAdmin tool per instance. I am planning on dropping > >code in the internal server web root for each instance to refresh app > scopes > >and such. > > DK > > We were thinking of going that route, too, since that's the only way we > can think of to hit a specific instance. It's a pain to have to do this for > app-specific (not general CFMX) reloading, though. (Some of my apps have > different interpretations for what "reloading" the application means: some > purge app-specific files, or do other fine-grained things.) > > Since I already have a hardware load balancer, it would be ideal if I > could keep sharing J2EE *sessions* but not the application themselves. I'd > sure like a definitive answer, if anybody knows it. If this isn't possible, > is there some other way to achieve the same overall goal? > > Thanks for your reply, Douglas, it's nice to know that somebody else is > giving this J2EE session sharing thing a shot. BTW, were you surprised to > see your Machine A serving up Machine B's code when you first enabled > session sharing? I sure was. :-/ > > Thanks, > Jamie > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:210261 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
