How to fix session getting null when multiple user request at same time in .net 6.0

Question

How to fix session getting null when multiple user request at same time in .net 6.0

Shailesh Thummar 0

Any solution for "Session getting null when multiple user visit the site" Error?

I analyze the iis worker process physical memory not exceed more than 3GB?

Lex Li (Microsoft) 6,037 Reputation points Microsoft Employee

2023-02-16T06:11:01.3566667+00:00

It's vague to say "Session getting null when multiple user visit the site". 1) When too many requests come in a short period of time, web apps themselves might experience a lot of issues if they were written in certain ways. That's why load testing is very important during development, and burst load should be part of the load testing plan to reveal such issues. The earlier you find them, the easier for developers to resolve them according to best practices. 2) Null session can be caused by too many factors, and burst load can amplify that. At this moment, I don't think 3-GB memory usage is that significant (as long as this is a 64 bit web app). If I were you, I would focus more on the null session by collecting more data (crash dumps or hang dumps) as well as the web app source code to rule out the common causes. You can open a support case via https://support.microsoft.com if you want further assistance.

1 answer

Your answer

Lex Li (Microsoft) 6,037 Reputation points Microsoft Employee

2023-02-16T06:11:01.3566667+00:00

It's vague to say "Session getting null when multiple user visit the site". 1) When too many requests come in a short period of time, web apps themselves might experience a lot of issues if they were written in certain ways. That's why load testing is very important during development, and burst load should be part of the load testing plan to reveal such issues. The earlier you find them, the easier for developers to resolve them according to best practices. 2) Null session can be caused by too many factors, and burst load can amplify that. At this moment, I don't think 3-GB memory usage is that significant (as long as this is a 64 bit web app). If I were you, I would focus more on the null session by collecting more data (crash dumps or hang dumps) as well as the web app source code to rule out the common causes. You can open a support case via https://support.microsoft.com if you want further assistance.

Answer 1

Hi @Shailesh Thummar，

I analyze the iis worker process physical memory not exceed more than 3GB

Based on your description, have you set a virtual memory limit of 3GB for the application pool? Something like this: enter image description here If this is the case, then this result is in line with expectations. When the memory reserved by the worker process exceeds this value, IIS will start a new process and recycle the old one. And in-memory session state is stored in the memory of the IIS worker process. So whatever state maintained by the worker process, including any session objects, is lost.

In this case, you may need to store session data outside of the IIS worker process, for example in SQL server.

Here's a good article that might help you: https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/iis-best-practices/ba-p/1241577

In addition, I found you have posted a similar thread, if they are the same issue, I will follow you here.

Best regards,

Xudong Peng

If the answer is the right solution, please click "Accept Answer" and kindly upvote. If you have extra questions about this answer, please click "Comment". Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Share via

How to fix session getting null when multiple user request at same time in .net 6.0

1 answer

Your answer