Session Timeouts & Application Pools

[dutton]

In regards to ticker #JKQ-58957-591, please review for details.

I have one client, which we run as a subdomain and who uses an ASP application that sets a session each time they login.

Now, I can control what the timeout is for the session within the application itself, however, I am stuck because of course the server has it's own session setting - which ends up over riding mine.

Support has put our domain in it's own application pool, this actually worked great for about 3 months. But all of the sudden, over the last two weeks, we are losing this application pool constantly and therefore, I have a yelling client on my hands.

Any ideas?

 

[Stephen]

2 Ideas.

1. Move away from using asp sessions as they are really, unreliable.
This is by far the best option for a long term happy customer.

2. Use ASP sessions but they may be unreliable at times, we can again try to stabilize this in your application pool, but all the settings look good.

I saw your ticket, the domain is already in its own pool and has a 90 minute session time, anything beyond 90 minutes puts an un-due stress on the server resources and can not be used, sessions are very memory hungry and will downright gobble up any free memory on a server.