umbraco.config File Locking in Multi-site installation without load balancing
I have a site with approx 4000 nodes in the node table, it is a multi-site installation but because of the binding requirements of SSL Certificates in IIS, each site is setup individually in IIS but points to the same place in the file system. It's taken some time to get a working solution due to other issues but I still have one outstanding problem.
Everytime a publish happens the web service is called on the other urls in the installation to force the in-memory cache to be updated however as part of this process all sites then try and write to umbraco.config at the same time resulting in errors along the lines of:
System.IO.IOException: The process cannot access the file 'D:\inetpub\wwwroot\example.com\root\App_Data\umbraco.config' because it is being used by another process.
I am looking for some ideas as to how to overcome this. My initial thoughts involve modifying the core to delay the web service call which I'd rather avoid for maintainability reasons. I wondered if anyone has any other suggestions?
Experienced the same issue with a single-site installation which had multiple persons logged in in the back-office... Although it's not exactly the same problem as you're experiencing, just wanted to note this.
Wasn't sure, I saw a very similiar thing in Elmah recently, my colleague who sits next to me who is off ill today dealt with it so I am not completely up with the details.
Are the separate IIS sites running under the same user (eg Network Service) or separate AppPool Identities? Or am I still totally missing the point?
Had a quick read through the various issues in the various threads, but I'll carry on reading through and at the very least see if we can verify this problem also here.
umbraco.config File Locking in Multi-site installation without load balancing
I have a site with approx 4000 nodes in the node table, it is a multi-site installation but because of the binding requirements of SSL Certificates in IIS, each site is setup individually in IIS but points to the same place in the file system. It's taken some time to get a working solution due to other issues but I still have one outstanding problem.
Everytime a publish happens the web service is called on the other urls in the installation to force the in-memory cache to be updated however as part of this process all sites then try and write to umbraco.config at the same time resulting in errors along the lines of:
I am looking for some ideas as to how to overcome this. My initial thoughts involve modifying the core to delay the web service call which I'd rather avoid for maintainability reasons. I wondered if anyone has any other suggestions?
Experienced the same issue with a single-site installation which had multiple persons logged in in the back-office...
Although it's not exactly the same problem as you're experiencing, just wanted to note this.
I should probably mention that this is a 4.7.0 installation.
Is this a Yellow Screen of Death type error or something from the Event Log?
Not a YSOD because the process happens in the background but it is in the logs and I get error notifications (via ELMAH) every time a publish occurs.
Wasn't sure, I saw a very similiar thing in Elmah recently, my colleague who sits next to me who is off ill today dealt with it so I am not completely up with the details.
Are the separate IIS sites running under the same user (eg Network Service) or separate AppPool Identities? Or am I still totally missing the point?
Had a quick read through the various issues in the various threads, but I'll carry on reading through and at the very least see if we can verify this problem also here.
If Chris get's in he may have more to add.
The seperate sites are all running under the same application pool and using the same AppPool identity.
of course they are yes sorry
will read and think more before responding any further
is working on a reply...