Hot answers tagged

15

Azure Redis cache is the default session provider Sitecore 9.0 will use in Azure Paas. Out of the box, Azure Redis Cache will be configured and used by Sitecore. Sitecore uses this session provider as a means of managing out of process (ie. distributed) session state to share contact data across browser sessions and devices. This is required to support ...


8

How we did for AWS, on Azure I think should be pretty the same: Create test1 page that will display server name(CD1, CD2, etc.) and put information to session: trigger some goal and save some information directly to session. For example something like: //Register goal var goalTrigger = Sitecore.Analytics.Tracker.MarketingDefinitions.Goals[{SomeGuid}]; ...


6

Shared session configuration is for Analytics Ths sessionState setting in the web.config setting manages the Redis storage for your Sitecore session. Instructions found here: https://doc.sitecore.com/developers/90/platform-administration-and-architecture/en/walkthrough--configuring-a-private-session-state-database-using-the-redis-provider.html


5

We managed to solve this issue with the help of Sitecore and Microsoft: Solution: Increase the min worker thread pool to xxx (where xxx should be greater than busy value on log) Increase PollingTime to 30. If above doesn't help upgrade the redis.stackexcahange to latest And increase sync timeout 5k, connection time 10k and retry timeout 6k (should be ...


5

It's not entirely clear if this is happening under load, but there are a number of troubleshooting steps and configuration changes you can make to optimise your Sitecore implementation with Redis. The out of the box settings often need some tweaking depending on your environment. Confirm the Redis cache is not under too much load. You ...


2

This blog post covers a great explanation from Sitecore about what's going on when you see exceptions like this and how to adjust config to fix the problem. The general approach as recommended by Sitecore seems to be first to apply support patch Sitecore.Support.210408 and config changes from here. A note that (in my opinion) they don't supply very good ...


2

UPDATE: Based on the updated stack trace, this actually looks like an issue with serializing an IEnumerable property exposed on one of your glass models (whether directly on your primary model, or indirectly as a child item's properties). One thing you can try to do is to replace all of your IEnumerable<T> definitions with a concrete collection type,...


2

We had the same kind of issues. We were able to resolve them by tweaking the polling interval of the private session state provider and increasing the timeoutBetweenLockAttempts of the shared session state manager. Private Session State: <sessionState mode="Custom" cookieless="false" timeout="20" sessionIDManagerType="Sitecore.SessionManagement....


2

We are using this same approach in our Sitecore solution. The main challenge we ran into is that the SecurityTokenValidated event from the OWIN middleware, where you receive the token, runs before the AcquireRequestState lifecycle event from IIS where the session state gets instantiated. Therefore we were unable to use the Sitecore private session state ...


1

If you are on managed cloud (Azure Paas), these are the config files that are referencing Redis App_Config\ConnectionStrings.config ("redis.sessions") App_Config\Sitecore\Azure\Sitecore.Analytics.Tracking.Azure.config (patch:attribute name="defaultProvider" value="redis") Web.config (sessionState configurations) Make sure to ...


1

Ken, good question. Sitecore maintains an ASP.NET Session state outside the process to share between CDs (in fact 2 session states). The session state is used to flush Analytics data to xDB on Session End. The problem, thought, only InProc ASP.NET provider supports/raises the event OOB. Therefore Sitecore had to cook their own providers. Point 1: do you use ...


1

You can find the Redis configuration for XC in the config.json under Caching/Redis: "Caching": { "Memory": { "Enabled": false, "CacheStoreName": "Commerce-Memory-Store" }, "Redis": { "Enabled": true, "CacheStoreName": "Commerce-Redis-Store", "Options": { "Configuration": "localhost", "InstanceName": "Redis" } } }


1

I think you also should change the shared session state as per Sitecore's documentation as having them different could cause this issue and other issues.


1

from support: Some Azure resources can call automatically and some cannot, unfortunately, Redis is one that cannot scale. Sitecore XP has no way of knowing what size Redis cache the customer is using so you will either need to set up an Alert using Azure Monitor for when Redis gets within a certain threshold or you should just size up permanently. You can ...


Only top voted, non community-wiki answers of a minimum length are eligible