Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We have a problem where the solution seems to be to recycle the app pool for a particular site (a CMS issue we have little control of, I won’t go into it here).
My question is that while this seems to work, if there are users on the site making payments etc, if we recycle will this kick them off?
Thanks
Duncan
In the basic setup, yes.
Assuming your storing whether a user is logged in via session state, the basic ASP.NET setup is to store session state in memory. Recycling the application clears the memory allocated for that application, including the session state.
However, if your session state is configured to not be stored in memory, for example in a database, then no, users should not be kicked off.