We developed an ASP.NET 2.0 application which is using a MySQL 4 database using the .NET Mysql connector.
The application uses forms authentication for user login and during development it worked fine.

Recently we host the application on a service provider, but after user logs in and having the application idle for about 5 minutes the session timouts and it redirects to the login page. The application uses a session variable where the username is stored about the user who logged in. The web.config section about session is the following:

Unfortunately the session does not last 20 minutes as specified but mostly 5 min. I tried StateServer mode instead of InProc changing the mode command in session state tag but the result is exactly the same.

I talked with the technical support to verify that no antivirus software is scanning the bin folder and they assured me about that. They also told me that the problem is caused by a problem in the application code and there's nothing more they can do! What's odd is that stateserver causes timeout of the session in about 5 minutes also.

I'm really stuck. Is there a solution to that, or do I have to find for another more valuable hosting provider

Thank you.

Hi, famous: 

Try to configure shutiing down time worker process after being idle according to the document:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgu...

The default time when the worker process will shut down after being idle for is 20 mins.
If you set session timeout for 1440s and it works in InProc mode,that is to say 24mins,maybe the worker process will restart after being idle for 20 mins,once the worker process restarts, the session data will be lost and it wil expire before the time setting in web.config.

I hope the above information will be helpful. If you have any issues or concerns, please let me know. It's my pleasure to be of assistance

This is because you are on shared hosting !!! The session variable here will depend on many things server side. For example, when the application pool recycle your sessions will be killed. This will happen in any overloaded shared hosting server...

Regards
 

Rex Lin - MSFT:

Hi, famous: 

Try to configure shutiing down time worker process after being idle according to the document:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgu...

The default time when the worker process will shut down after being idle for is 20 mins.
If you set session timeout for 1440s and it works in InProc mode,that is to say 24mins,maybe the worker process will restart after being idle for 20 mins,once the worker process restarts, the session data will be lost and it wil expire before the time setting in web.config.

I hope the above information will be helpful. If you have any issues or concerns, please let me know. It's my pleasure to be of assistance

 

Thank you very much for your reply.
Well, unfurtunately due to shared hosting I do not have access to advanced IIS configuration e.g. the application pool.

I tried the StateServer mode but unfortunately I have the same issue. When in StateServer mode the application still depends on the worker process, like the InProc mode?
I want to contact the hosting company for the issue but I do not know what to tell them to setup. I try to figure out the reason this is happening. They claim that there's nothing more for them to setup.

Oh the url you specify is not working

Tell them to isolate your domain into a new application pool.

Also, make sure that they don't use the web garden feature.

Regards 

Pls help me out ... I am desperate and my life sucks here....