I'm using Umbraco 6.0.3 via web hosting provider, whereas my Umbraco instance is running on multiple IIS processes. My problem is, that when I'm publishing content on the live site, the result is confusing: new data appears, then disappears, contents are shown up randomly, so there is the possibility to loss data. Results of multiple people contributing on the same site are unpredictable.
The effect is reproduciable on a local site as well (Win7 ultimate / IIS 7.5.7600.16385):
In IIS, increase the "Maximum worker processes" to 5, for example. Now make changes on the admin interface. Even just using the admin interface, you will see your newly created items/types/anything appear/disappear. The same goes on with the fronted: Published pages are sometimes visible, sometimes not. It depends on which worker process is serving the contents.
As I wrote in my first post, I'm using a hosting provider, not my own installation. The fact, that a provider is using multi process mode is something I can't change. Of course, I can pay for different packages. Because of this, I can't use powershell scripts either.
The problem is that each worker process will have it's own cache. So say you make a change in content on worker process 1. Only the cache of worker process 1 will be updated, all other 4 procesess will not know about the content change.
I still think the best solution is to contact your hosting provider and see if they can make the change.
Cache problems using 6.0.3
I'm using Umbraco 6.0.3 via web hosting provider, whereas my Umbraco instance is running on multiple IIS processes. My problem is, that when I'm publishing content on the live site, the result is confusing: new data appears, then disappears, contents are shown up randomly, so there is the possibility to loss data. Results of multiple people contributing on the same site are unpredictable.
Settings I'v made in umbracoSettings.config:
<XmlCacheEnabled>False</XmlCacheEnabled>
<ContinouslyUpdateXmlDiskCache>True</ContinouslyUpdateXmlDiskCache>
<XmlContentCheckForDiskChanges>True</XmlContentCheckForDiskChanges>
I got no knowledge, what servers are used to run my site.
What can I do to have different IIS threads in sync while serving the site?
Hi Arpicheck
Is the site running on different application pools?
/Jan
Hi Jan
As far as I know, processes serving the site are running in the same app pool.
Arpicheck
The effect is reproduciable on a local site as well (Win7 ultimate / IIS 7.5.7600.16385):
In IIS, increase the "Maximum worker processes" to 5, for example.
Now make changes on the admin interface. Even just using the admin interface, you will see your newly created items/types/anything appear/disappear. The same goes on with the fronted: Published pages are sometimes visible, sometimes not. It depends on which worker process is serving the contents.
May this have connection with sessions? Sessions are configured InProc by default...
By assigning multiple worker processes you are setting up a "web garden". This is not supported by Umbraco.
See these posts :
http://our.umbraco.org/forum/core/general/22383-Using-Umbraco-47X-in-an-IIS-web-garden
http://our.umbraco.org/forum/getting-started/installing-umbraco/15368-Umbraco-in-web-garden
If performance is an issue you can always consider to set up a "web farm" and configure load balancing.
http://our.umbraco.org/wiki/install-and-setup/installing-umbraco-for-load-balanced-environments
The only thing you need is some way to sync your media files. I used this powershell script with success :
http://edoxy.net/Blog/50-Umbraco-replication.html
Dave
Hi Dave
Thank you for your suggestions.
As I wrote in my first post, I'm using a hosting provider, not my own installation. The fact, that a provider is using multi process mode is something I can't change. Of course, I can pay for different packages. Because of this, I can't use powershell scripts either.
Maybe you contact your hosting provider and ask them to lower to worker processes for the app pool to one ?
Dave
Yes, this is a solution, which as I mentioned above is accessible trough priced packeges. Or maybe I have to find another provider :)
But there is something I really can't understand: if this is because of caching in the backgroud, why I'm unable to turn off this behaviour?
The problem is that each worker process will have it's own cache. So say you make a change in content on worker process 1. Only the cache of worker process 1 will be updated, all other 4 procesess will not know about the content change.
I still think the best solution is to contact your hosting provider and see if they can make the change.
is working on a reply...