Sitefinity’s integration with OpenAccess ORM allows you to benefit from the OpenAccess implementation of Data (Level2) Caching. Data caching provides a mechanism for storing the results of a query to the database in cache and serving them from cache when the same query is executed for that context. This results in faster performance when retrieving data.
As of Sitefinity CMS 7.1, Data (Level2) Caching is enabled by default.
You can see the value of the data caching property by opening Administration » Settings » Advanced » Data and checking the EnableDataCaching property.
If the input field is empty, Sitefinity CMS automatically sets this value.
Sitefinty’s load balancing feature facilitates handling of the cache synchronization, which is necessary when the application runs in Load Balanced scenario.
Sitefinity CMS uses web services communication to notify all participating nodes when a content change occurs. This way it is guaranteed, that this content change propagates to all instances in your load balancing setup.
To setup the web server URLs, perform the following:
NOTE: In order for the load balancing cache synchronization to work properly, the specified server nodes must be visible and able to message each other. Make sure that your network infrastructure and/or firewall settings allow this
An exception of type 'System.Exception' occurred and was caught.
Type : System.Exception, mscorlib, Version=184.108.40.206, Culture=neutral, PublicKeyToken=b77a5c561934e089
Message : Error sending system message to URL: http://192.168.1.85/Sitefinity/Services/LoadBalancing/SystemWebService.svc/HandleMessage; HTTP method: PUT; Host: null
Check the InnerException data for this exception:
This means that there was a problem accessing the LoadBalancing service on one of the other nodes, and usually indicates a network problem in the nodes visibility. Ensure the nodes can communicate with each other and no firewall is blocking the service.
This means that the LoadBalancing service request was not authenticated correctly. This usually indicates incorrectly configured settings of the Security Configuration. Ensure you have followed the instructions correctly.
Back To Top