Re: session state variables expiring too quickly

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Check your <processModel responseDeadlockInterval setting
and set a maximum value that is at least the same as your longest
application-level timeout setting.

responseDeadlockInterval="hrs:mins:secs|Infinite"

In your case, that would be :

responseDeadlockInterval="2:00:00"
since you have set your session timeout for 120 minutes.

This may not be the specific solution for your p[roblem,
but it may be one less thing to worry about, and it doesn't
cost you anything to try it.

When the ASP.NET worker process has been idle for the duration that is
specified in the responseDeadlockInterval configuration setting, it causes
the deadlock detection mechanism to restart the worker process, losing your
session data if you're running sessionState Inproc.



Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
======================

<bennett@xxxxxxxxxxxxx> wrote in message
news:1117702758.121690.200010@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> In the web.config file for my application, in the <sessionState>
> section I have set timeout="120" (in minutes), but session state
> variables in my application seem to be expiring in about 5 minutes.
> Any idea what could cause this?
>
> I have the mode="InProc" attribute set for <sessionState>. I know that
> some people have solved the problem of session variables timing out too
> quickly by changing that attribute, but I cannot use mode="StateServer"
> because my ASP.Net host doesn't support running a state server on the
> shared host, and I can't use mode="SQLServer" because I don't have the
> admin rights on my host's SQL Server to set up the SQL Server session
> state database. (I tried running the InstallSqlState.sql script on my
> host's SQL Server database and got a bunch of access denied errors.)
>
> I realize this can happen occasionally if the server is rebooted or
> ASP.Net is restarted, but with my host's server it's consistent; the
> values *always* die within five minutes. One thread at
> http://www.gotdotnet.com/Community/MessageBoard/Thread.aspx?id=17380
> suggested that sporadic dying of session state variables might have
> something to do with an anti-virus program running on the host, but in
> my case it happens every time.
>
> I'm developing the app on my local IIS Web server and then using Visual
> Studio's Project->Copy Project function to copy the project to the
> remote host. When the application runs on my local machine, the
> session variables do not time out in 5 minutes, but when it's copied to
> the remote server, they do. This leads me to think it's not something
> in the project files but some configuration setting in IIS, but the
> question is, what? More importantly, is there something I can change
> in my project to make session state variables last longer in all cases,
> independent of whatever IIS setting is breaking it?
>
> My host says that in the Properties for my web site in IIS, they have
> the HTTP "Connection timeout" set to 120 (expressed in seconds; the
> default is 900). (This is not the same as the session timeout
> setting.) Could that have anything to do with it? But I tried setting
> connection timeout to 120 on my local IIS and my local application's
> session vars still didn't die after 5 minutes. (I wouldn't expect the
> Connection timeout to have anything to do with it anyway, because I
> thought ASP.Net uses cookies -- or query strings in the case of
> cookie-less sessions -- to associate your browser with your current
> session, and that will work even if the HTTP connection dies, as long
> as your session hasn't expired on the server yet. Wouldn't it?)
>
> Any help would be extremely appreciated,
>
> -Bennett
>


.

Relevant Pages

  • Re: IIS / TCP RST instead of FIN
    ... IIS / TCP RST instead of FIN ... We have a similar problem with the behavior of the IIS. ... This type of server behaviour is likely responsible for many of the responder RSTs observed in the ... http.sys wrote that there was an idle timeout and that the session was closed. ...
    (microsoft.public.inetserver.iis)
  • Re: Application Pool timouts.
    ... a) From what i understand, the application pool timeout is the timeout for ... an idle session which is created by a browser. ... is idle for 20 minutes or longer the problems occur. ... Application Pool's w3wp.exe process to be shutdown by IIS when no requests ...
    (microsoft.public.inetserver.iis.security)
  • Re: How do I change the session timeout?
    ... Ok, it might not IIS itself, but ASP.NET, that runs in the IIS environment, that does that. ... Prove that my sample code isn't valid by supplying us with code which proves you're right. ... What you are demonstrating is that the timeout is occuring at one minute ... When the application starts at the same time as the session, as in your test, it doesn't prove ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: RWW/Connect to my computer at work issue
    ... IIS Timeout Configurations. ... verify if the SBS server has been configured properly. ... Step 2: Check IIS Timeout Configurations ...
    (microsoft.public.windows.server.sbs)
  • Re: CGI under IIS throws away printf on multiple posts.
    ... IIS is not throwing away anything. ... will have to implement in CGI, by taking a server-side lock to prevent the ... session from performing the operation a second consecutive time. ... "application session" (IIS is a high-performance server. ...
    (microsoft.public.inetserver.iis)