Since moving to BV5 (from SF6) I've noticed a high incidence of losing my session. At least once a day I will be navigating the Admin area and will have to log in, even though my browser has only sat idle for maybe 1 minute, sometimes not at all. I'm having my host look at the logs to see if they can see anything, but was wondering if anyone esle saw this or had a clue.


I'm also wondering if it has anything to do with some invalid postback errors I'm seeing with customers on the cart page. Not sure what they are doing, but it's a validation issue - so I'm wondering if they are doing something and losing their session and that is what is causing the validation error.

Host is saying that a "User Session XXXX" -- where there is a number in place of XXXX (different each time) has reached some sort of time limit and forced an application recycle, even though it happens after only minutes (or less) of activity.

Joe, is the site sharing an app pool with any other sites?

How is your app pool setup?

By default a .NET site will recycle at least once a day and can be controlled as to when.

Does the box have plenty of RAM on it?

Is SQL on the box?

The timeout you mention does not recycle the application. It only drops a single session from the session manager when the timeout expires. For example, if 3 people visited your site and only 2 are active, the 3 third session would be dropped after 20 minutes of inactivity. Note that the 20 minute timeout only applies if you are storing sessions in-memory (the default).


On the other hand, if the application is recycled, then all in-memory sessions are dropped.



I think what Noah was getting at, is there are many reasons for an application to recycle: memory exceeded, session count exceeded, running time exceeded, exception exceeded, and many more. Your site might be recycling for several reasons (which would explain why it seems to recycle often). But regardless of the reason, when the application recylcles, all of your in-memory sessions are dropped.



To really solve this, you need to get to the bottom of why the application is recylcing, and then deal with each issue.

I say "heavy load" -- but that isn't much -- I only have perhaps 8 concurrent users at any given time. The box has 1G of memory. SQL is on another server -- which is at a co-location facility, and we are looking at switching to another SQL server in the same facility to see if they slight delay isn't causing the issue.

Yes -- that was a year ago! :-)

If I remember correctly, it was just fine tuning the site and locating the SQL database on a server in the same location as our data server.