views:

129

answers:

2

Hello

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

+2  A: 

If you're using InProc session state, their sessions will be abandoned, so yes they may be kicked/logged out. If this is becoming a problem, consider using StateServer or SQLSessionState session modes.

JonoW
We are using database session state, though not the 'official' sql session state. The site is half-legacy ASP and half .NET (the legacy ASP part is where the e-commerce is)
Duncan
In that case, as long as you're not accessing the built in Session functions directly, it shouldn't kick them out. Are you setting your own session cookies?
JonoW
I don't think so, imagine we are using the standard session cookies.
Duncan
+3  A: 

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.

Sekhat