The above is a simple representation of a configuration that i have set up for a site and I am getting strange behaviour that I do not understand and hope to get some more understanding here.
Web 1 and Web 2 are virtual web servers running windows server 2008 R2 Enterprise edition with Service pack 1 installed that both point to a single file share on a separate machine. There is also a separate database server.
The situation - I can navigate to the admin section of Web 1 and make some content changes, publish them and they are immediately available on Web1. The umbraco.config file is correctly updated as expected.
However, Web 2 does not reflect these changes immediately. In IIS7 on both servers Response caching has been turned off at the server level and the site level. I have also tried setting "Maximum cached response...." to 0. Once I do an IIS reset, the content in available on Web 2 but for obvious reasons this is not a solution.
So my question is, where could this caching be heppening? Are there some other settings in umbracoSettings.config or elsewhere that I should be looking at to alleviate this problem?
There is built in caching into nforum, to be honest I went a little over the top - Something which I'll be revisiting. Personally I'd set the cache time to 0 in the nforum code and see if that helps, to do this look in 'CacheHelper.cs' and you can set the following line to '0'
Did you remember to set up the DistributedCalls in the umbracosetting.config? When Web1 updates the umbraco.config file, then it needs to "ping" Web2, for the changes to be reflected on that server as well.
Caching umbraco.config and umbracoSettings.config
Hi All
The above is a simple representation of a configuration that i have set up for a site and I am getting strange behaviour that I do not understand and hope to get some more understanding here.
Web 1 and Web 2 are virtual web servers running windows server 2008 R2 Enterprise edition with Service pack 1 installed that both point to a single file share on a separate machine. There is also a separate database server.
The situation - I can navigate to the admin section of Web 1 and make some content changes, publish them and they are immediately available on Web1. The umbraco.config file is correctly updated as expected.
However, Web 2 does not reflect these changes immediately. In IIS7 on both servers Response caching has been turned off at the server level and the site level. I have also tried setting "Maximum cached response...." to 0. Once I do an IIS reset, the content in available on Web 2 but for obvious reasons this is not a solution.
So my question is, where could this caching be heppening? Are there some other settings in umbracoSettings.config or elsewhere that I should be looking at to alleviate this problem?
Thanks
Bradley
There is built in caching into nforum, to be honest I went a little over the top - Something which I'll be revisiting. Personally I'd set the cache time to 0 in the nforum code and see if that helps, to do this look in 'CacheHelper.cs' and you can set the following line to '0'
private const int Cachetimeinminutes = 1440;
Did you remember to set up the DistributedCalls in the umbracosetting.config? When Web1 updates the umbraco.config file, then it needs to "ping" Web2, for the changes to be reflected on that server as well.
is working on a reply...