Right here's hoping that this doesn't start another thread as this is getting embrassing!!!
That second set are logs are obviously related to the drop of the instance and JRun starting to hand the sessions across to the other server. Not very helpful but still more information I can work on. Yes you're right we do have another instance on that server and yeah it is strange that out of four instances only one is failing. Or what I should say is that the vast majority of fails are coming from there, we do get a few others "here and there" but nothing worth highlighting as an issue and related to this. We're going to move the code from the other instance over to this one in the hope that this might fix it. The idea being that we might have a mismatch somewhere that is causing a problem so this would eliminate it this. Stab in the dark really though :-(. Don't know about the shared VM side of things, I'll need to ask the System's guys about that one but again that kind of opens up the field to anything while we've definately got a lead with the JRun logs at the moment. Thanks for your efforts though Brad, it's appreciated. Cheers, James >Interesting. I've got to give credit to someone at Macromedia for using >the work "breakage". :) >Well, it seems clear that IIS and the JRun connector are losing contact >with the instance and subsequently removing it from the cluster. What >we don't know is why. Did I understand that you have at least one other >CF instance on the same physical box which does not experience this >problem? That would rule out OS and general connectivity problems. I >think you said it was on a VM. Is that instance along on the VM, or are >there more than one instance on that VM. I don't know where to tell you >to go from here. Maybe someone else will chime in with an idea. > >Just ignore my comment about the "dedicated IIS box". For some reason I >had gotten it in my head that you had a separate physical server for >IIS. I guess I've got the load-balancing diagram stuck in my head that >was posted yesterday on the list. :) > >~Brad > >down" > >The log file was from the failing instance. It was residing in the >C:\JRuns\Logs\ folder. > >IIS is sitting on both boxes so I'm not sure if that classes as a >"dedicated IIS box". We have round robin on the DNS as well so requests >are being passed to both boxes. > >I actually didn't know about those logs. You learn something new every >day :-) > >Just looking at the same time as those previous logs these start 2 >milliseconds after the failure notice. Nothing was happening in these >logs for a few hours before this... > >C:\JRun4\lib\wsconfig\1\LogFiles\jrun_iis6_wildcard080227.log - > >2008-02-27 10:50:43 jrISAPI[2192:6480] Sticky session breakage, a host >for ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;160198600;22374440;w Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:300094 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
