Outputcache not working on prod

Vote:
 

Hi!

I added [ContentOutputCache] to my controls I wanted to cache and everything is working on test. 

Moving on to prod the page doesn't get cached. Been reading this excelent post [link removed by moderator] by Mattias Löström and it seems I have something updating the db because the expire time in the web page header is correct (Now + cache time) but @EPiServer.CacheManager.Get("DataFactoryCache.Version") gets updated for each request.

Now the question is where do I go from here? How to I find what could be updating the db?

Prod is loadbalanced so was considering if it could be that but it should only send updates if the page is saved right?

Anyone got any ideas what to check?

#87798
Edited, Dec 11, 2019 7:51
Vote:
 

Hmm..

Removing the RemoteEventServiceEndPoints got it working.. so... Then I guess the question has evolved to. What is needed to make OutputCache work on a Loadbalanced enviroment?

#87799
Jun 23, 2014 19:59
Vote:
 

I don't have access to prod at the moment so just running some ideas by the community while I wait for my slot.

As of 7.5 we no longer add a <site> definition in the episerver.config. Does this also mean that I no longer add more then one RemoteEvents service on the webconfig?

#87826
Jun 24, 2014 10:23
Vote:
 

I think the outputcache directive in a usercontrol is a pure asp.net thing and will work regardless of the server setup...

#87829
Jun 24, 2014 10:49
Vote:
 

Well it is and it isn't =)

EPiServer does some magic of it's own. But relies on the outputcache in MVC in the background. 

The issue for me was that the DataFactoryCache wsa getting updated so Epi told the outputcache to serve a new version all the time. This because the RemoteEvents was wrong.

Apparently you only need one service per site now that the sites are added within the Admin mode. Removing the second one we had (had two sites and was using TCP) made the cache work. Initial testing also seems to show that the cache for the second site still gets updated. So seems to work.

#87832
Jun 24, 2014 11:11
Vote:
 

Seems I spoke to soon. 

Removing one of the services just hade it happen less offen (read every third second) instead of every second.

#87844
Jun 24, 2014 13:30
Vote:
 

So time for an update.

The issue seems to go away when I remove the third server. So two servers running either udp or tcp works fine. The cache holds.
Adding a third makes the datafactory cache jump.
#87872
Jun 24, 2014 17:36
Vote:
 

Workaround atm is to just let one server broadcast messages making this the Edit server.

#87931
Jun 25, 2014 18:21
Vote:
 

Hi! o
one loose thought, are there other sites (cms 6) running in parallel on the servers? Try changing your portnumber in the 7.5 config to 5050 or something other than 5000

#109748
Oct 14, 2014 11:12
Vote:
 

http://world.episerver.com/Support/Bug-list-beta/bug/118503

#109787
Oct 15, 2014 9:19
Vote:
 

I can confirm that we have found and fixed a bug that effects output cache. The fix is planned to be released in upcoming 7.15.0 release (soon available)

#109861
Oct 16, 2014 9:58
Vote:
 

Glad to hear it. The fast release cycle sure pays off. Great work!

#109869
Oct 16, 2014 10:17
Vote:
 

I can't seem to see the detail with what http://world.episerver.com/Support/Bug-list-beta/bug/118503 fixes.   Is there a link with more detail?

#114953
Jan 05, 2015 19:51
Vote:
 

bug list no longer beta, this link should work:
http://world.episerver.com/support/Bug-list/bug/118503

#114979
Jan 07, 2015 8:44
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.