volume_up

A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More. 

volume_up

A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More. 
AI OnAI Offsmart_toy

Caching not working in Azure

Mari Jørgensen
Mari Jørgensen
Vote:
expand_less 0 expand_more

We are using Find heavily on our site, and have added caching using 

.StaticallyCacheFor(TimeSpan.FromMinutes(_defaultCacheTimeInMinutes)) // for GetResult()

or

.GetContentResult(cacheForSeconds:3600, cacheForEditorsAndAdmins:true) // for GetContentResult()

I have added proxy settings to web.config and verified that caching is working locally (query is exceuted once).

But on Azure we get a lot of errors indicating that the results are not cached (EPiServer.Find.ServiceException: The remote server returned an error: (429) Too Many Requests.)

Anyone seen similar behavior? Or know what to look for?

#189549
Mar 20, 2018 15:17
Vote:
expand_less 0 expand_more

According to Quan's post from August 2017 there is a bug in .NET 4.7: https://vimvq1987.com/episerver-caching-issue-net-4-7/ 

We are running Episerver.Find version 12.5.3. The Azure env. is running .NET 4.7.1, where this .NET bug is fixed.

#189552
Edited, Mar 20, 2018 15:30
Jonas Bergqvist
Jonas Bergqvist
Vote:
expand_less 0 expand_more
#189586
Edited, Mar 21, 2018 7:46
Vote:
expand_less 0 expand_more

Thanks for the update, Jonas. Yes, we confirmed yesterday that the issue disappeared when scaling down to 1 instance. 

#189587
Mar 21, 2018 8:25
error This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.