![]() In your case as you are considering to implement a Caching solution for session management in near future, our recommendation is to move to a single instance as a workaround for now. "Azure Web Apps is a stateless platform and our recommendations is to implement a Session Management solution that best works for your environment and avoid the dependency on In-memory session state management especially in cases where your Web App is hosted on multiple servers. Reached out to support with an Emergency ticket – the response is: Lets say – my session Id is “1eocgtmwwwwvs1cxksyofne4”, after the page refreshes it got changed to “5p1hsxszq2mcqmt5i5ytqg12” including all other information that are managed in session variable. After many attempts, we reproduced the issue – surprisingly sessions are getting swapped. To debug this issue, we started printing the actual sessionId in the page. It injects ARR affinity cookie in the Http response that helps in redirecting a user to the same instance with which it established the session at the first time. We didn’t go for a separate out of proc session manager (Redis cache / DB based) on the day 1 because, according to the documentation, Azure Web app runs with a sticky session load balancer (when running with multiple instances) by default. ![]() We were wondering how that can happen since we are maintaining the sessions in "in proc". We started getting complains from the users that intermittently users are experiencing some issues which can cause only if they lose the session variables while actively using the site. We marked the site in Auto scale mode with 2 minimum instances. I did a production release for one of my clients with Azure PAAS – Azure Web App (formerly Azure Websites). ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |