Why Session timeout does't work?.
i have set the session time out in web.comfig file as
<sessionState mode="InProc" cookieless="false" timeout="20" />
it doesn't work at all , I just let open the window, look at the clock if
I do nothing , 10 minutes later I am thrown away from the session , the values
are lost !
how can I do that ?, I really need a longer timeout
how do i do it?.
Re: Why Session timeout does't work?.
I'm having a similar problem. If you have figured this out or if you figure
it out... can you forward the answer to me? I'll do the same!
"srikan11" <firstname.lastname@example.org> wrote:
>i have set the session time out in web.comfig file as
><sessionState mode="InProc" cookieless="false" timeout="20" />
>it doesn't work at all , I just let open the window, look at the clock if
>I do nothing , 10 minutes later I am thrown away from the session , the
>are lost !
>how can I do that ?, I really need a longer timeout
>how do i do it?.
i too have the same session timeoutproblem if i get a solution i will put it up here and if u get it then please put it here or mail at (gaur.seema at rediffmail.com).
Even i am struggling with this problem and dont know the solution yet
i am using session variables that i set in global.asax and then i set it to any value to identify that login is validand i check it in all pages whcih can viewed only after login.
In web.config file: U can set the session state timeout value.
And also set <pages enableSessionState="true"/>
i hope it helps
I have same problem. I use asp , when I set up session.timeout = 480 in common.asp file. it doesn't work at all . can someone help for this problem with asp? how can I fix this problem??
In .NET, there is an additional setting for this. The default script timeout is set to 90 seconds by the httpRuntime section of the machine.config file. You can change this setting to affect all applications on your site, or you can override the settings in your application-specific web.config as follows:
<httpRuntime executionTimeout="9000" />
The .NET config files are usually stored in the folder C:\Windows\Microsoft.NET\Framework\[version]\Config where [version] is the version of the .NET Framework such as v1.1.4322. You may need to restart IIS for such changes to take effect.
If this is an option or solution for this question. I found it on first google search I did.
Go to the website in question, right-click and choose "Properties".
Click on the "Home Directory" tab
Click on the "Configuration" button
Click on the "App Options" tab on the pop-up window
Choose the session timeout you wish. As you can see on this screen, the
default value built into IIS 5.0 out of the box is "xx" minutes.
Last edited by Czew; 04-21-2008 at 02:38 PM.
I had the same issue, and it seems the problem has to do with resetting IIS. Until the web server is restarted, the server settings of 20 minutes still remained.
When project is running in DEBUG mode all timeouts are disabled.
So, try this:
1. In web.config file: <compilation debug="false" defaultLanguage="your project's lenguage">
2. Run project in RELEASE mode.
Hope this helps.
Thanks a lot for posting.
After my last post, I realized the timeout was still stopping at 20minutes, and thought that somehow the timeout value was being bounced back and forth between the web.config and the server setting.
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL