It appears that when there are more than enough users signed in the sessions get reset in my Classic ASP application.. Why do you think this is?
The Application pool was set to Classic instead of Integrated, not sure if this has any affect on it?
I'm looking everywhere and cannot find what may be causing it. I set recycling in the app pool to OFF, and it still does a session reset, people are saying when it's busy usually.. So that means something.. Anyone?
There are other sites in the webserver, and the only thing in the event log shows this around the same time:
A worker process with process id of '6120' serving application pool '...' was shutdown due to inactivity. Application Pool timeout configuration was set to 20 minutes. A new worker process will be started when needed.
Do these other sites affect the session reset problem i'm encountering?