Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / General / February 2008

Tip: Looking for answers? Try searching our database.

Session Timeout, not working

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Scott - 19 Feb 2008 22:20 GMT
I have set the session timeout something greater then 20 minutes in
the web.config(120 minutes for testing) after 20 minutes to 30 minutes
click a button and am redirected back to the login.  My Session is
reporting 120 minutes I know this becuase I display on a debug page.
below are the 2 areas in the web.config that I set anybody tell me
whats wrong or what is missing.

<sessionState mode="InProc" regenerateExpiredSessionId="false"
timeout="120">
        </sessionState>

<forms name=".GSNAUTH" loginUrl="Login.aspx" path="/"
protection="Encryption" timeout="120" slidingExpiration="true"/>

When previeing on the page I see the top 1  becuase I have been able
to adjust it down to 60 minutes or 35 minutes whatever.

When I display on the debug page I show
lblSessionTimeout.text = Session.Timeout;

NOt sure what I am missing.
Anthony Jones - 19 Feb 2008 22:44 GMT
> I have set the session timeout something greater then 20 minutes in
> the web.config(120 minutes for testing) after 20 minutes to 30 minutes
[quoted text clipped - 17 lines]
>
> NOt sure what I am missing.

Unless you have other clients creating activity on the site your Application
Pool is probably timing out.  When a pool has seen absolutely no activity
whatsoever it can shutdown.  Check the settings on the pool to which your
application belongs.

Signature

Anthony Jones - MVP ASP/ASP.NET

Peter Bromberg [C# MVP] - 20 Feb 2008 01:19 GMT
Session expiration and forms authentication timeouts are two separate and
distinct things. Being redirected to a login page is a forms authentication
timeout issue, unless somehow you are also using session to do this.
Your ASP.NET application can recycle for any number of reasons, and when it
does, all inProc Sessions go bye-bye.
-- Peter
Site: http://www.eggheadcafe.com
UnBlog: htp://petesbloggerama.blogspot.com
Short Urls & more: http://ittyurl.net

> I have set the session timeout something greater then 20 minutes in
> the web.config(120 minutes for testing) after 20 minutes to 30 minutes
[quoted text clipped - 17 lines]
>
> NOt sure what I am missing.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.