We have site running on v8.1.1 and every now and then after a deploy (using azure devops) we get the following error:
System.IndexOutOfRangeException: Index points outside the properties array, which means the properties array is corrupt.
at Umbraco.Web.PublishedCache.NuCache.PublishedContent.GetProperty(String alias) in d:\a\1\s\src\Umbraco.Web\PublishedCache\NuCache\PublishedContent.cs:line 317
We have to recycle app pool then it site fires up.
In the Umbraco source we have:
if (index >= PropertiesArray.Length) // should never happen - properties array must be in sync with property type
throw new IndexOutOfRangeException("Index points outside the properties array, which means the properties array is corrupt.");
the main thing is asking nucache to rebuild at the end of an import,
but we've also tried to reduce the number of times we hit an item save because it appears they cause cache rebuilds even if the underlying item hasn't changed, so this should reduce the number of times we cause a cache rebuilt to occur.
nucache 500 error after deploy
We have site running on v8.1.1 and every now and then after a deploy (using azure devops) we get the following error:
at Umbraco.Web.PublishedCache.NuCache.PublishedContent.GetProperty(String alias) in d:\a\1\s\src\Umbraco.Web\PublishedCache\NuCache\PublishedContent.cs:line 317
We have to recycle app pool then it site fires up.
In the Umbraco source we have:
Anyone seen this before?
Regards
Ismail
Hi
Can't tell at the moment if this is an uSync issue or something within the Umbraco Core... we have an issue here
https://github.com/KevinJump/uSync8/issues/40
we are going to see what we can reproduce/figure out.
Just to update,
Have upgraded to latest version of usync but still get same issue. The error seems to occur in one of our components where we have the following line:
I am guessing that is then getting at nucache?
Hi,
we have pushed v8.2.2 release of uSync out, hopefully with some mitigation of this issue
https://github.com/KevinJump/uSync8/releases/tag/8.2.2
the main thing is asking nucache to rebuild at the end of an import,
but we've also tried to reduce the number of times we hit an item save because it appears they cause cache rebuilds even if the underlying item hasn't changed, so this should reduce the number of times we cause a cache rebuilt to occur.
feedback on this most welcome.
is working on a reply...