The httpRuntime executionTimeout attribute is expressed
in seconds, so it can hardly have an effect for the session
setting you want.
You could be creating a performance bottleneck
by specifying 7200 for httpRuntime executionTimeout,
since that's the "choke" time for a request which isn't
being completed.
Set it back to 90.
The web.config value you need to set, if you need 2 hours
duration for your sessions, is the sessionState timeout :
<sessionState timeout="120" />
Be forewarned that this setting ( 120 minute session-length )
will require quite a bit more memory resources than the
20 minute default setting.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
======================
"lekshmi" <an*******@discussions.microsoft.com> wrote in message
news:4f****************************@phx.gbl...
In my machine.config file, httpRuntime
executionTimeout="90".
and it dosent have <location> attribute nad
<allowOverride> attribute.
But my thread dies off after 1hr.
In the web.config, i have given httpRuntime
executionTimeout="7200"
Why is this happening?