We have moved to GitHub Issues
Created by Shannon Deminick 16 Sep 2014, 00:09:09 Updated by Paul Aikman 15 Jul 2015, 09:41:36
Relates to: U4-5492
Relates to: U4-2633
In most cases each server's IIS site taking part in a load balanced environment will have a different HttpRuntime.AppDomainAppId. However there are definitely scenarios where this is not the case and therefore a distributed call to a 'slave' server that has the same HttpRuntime.AppDomainAppId as the 'master' server will not have it's cache refreshed.
Fixed in rev: 7437240d096dbec6086dea64efeb29b27e19458a
Posts with work arounds:
For those in need, we built a custom 7.1.6 build with only this fix added. We've tested and it works great for us.
I am having issues with Umbraco 6.2.4 and distributed publishing. I need to publish twice to distributed servers to have their Examine indexes updated correctly. It looks like the XML cache if not refreshed in time. Is this likely to be fixed in a version 6 build after 6.2.4?
As per my last msg on the other thread, if this is an issue that you can replicate, you'll need to create an issue for it with all of the required details.
Similar to @Zac above, for anyone who needs a custom 7.1.8 build with only this fix: https://github.com/alluran/Umbraco-CMS/tree/7.1.8-U4-5491
Just encountered this issue. For the workaround there is no need to delete the site and recreate it. The site ID can be edited in IIS advanced settings
good to know, thanks!
Isn't this fix included in Umbraco v6.2.5? I think this really should be backported to Umbraco v6...
It's not ported back to 6.x, you'll need to use the workarounds described in the our posts above, this one's probably the simplest:
@Shandem I've used the work-around for a while, but now I need to introduce SQL Server Session State, which demands the AppId in IIS to be the same for every application in order for shared sessions to work. So right now it's kind of impossible to get v6.X working on a load-balanced environment with Session sharing... Now what? Should I do a custom build? Or is this important enough for a v6.2.6 for instance?
You'll probably need a custom build yes. Happy to accept a PR with the back ported changes for the dev-v6 branch so at least the code you are working with will be in the main Umbraco repository just in case there's any future security releases that need to be made, the change will exist there.
Ouch :-( I'll see what I can do to create a PR.
@kipusoep wondering if this fix was merged back in for Umbraco 6? Facing the same situation as yourself!
@firstname.lastname@example.org Nope, it's completely silent unfortunately: https://github.com/umbraco/Umbraco-CMS/pull/669
@kipusoep arg! A bit of a pain to manage custom builds in a world of NuGet references and package updates. Thanks for the fix though!
you can do a custom build with a new build number and host on myget, that should work pretty seamlessly for you.
@Shandem thanks, I'll give that a go,.
Assignee: Shannon Deminick
Backwards Compatible: True
Affected versions: 6.2.5
Due in version: 7.2.0