Home About Me Contact Me RSS ATOM

MVP Image

- Posts By Category

- Posts By Date

- Search The site


Subscribe by Email

- Sites I visit


Locations of visitors to this page

- Recent Blogs

Mystries of when does Session_End event fires in Asp.Net
Session_End and mysttries on when does it fires in Asp.Net
Posted on 10/2/2007 11:52:03 AM in #ASP.NET 2.X

Hi,

Following my post on few interesting things about session in Asp.Net many people asked me about the Session_End event. You can read the earlier post here.

Many people have asked me on exactly what are the reason for which the Session_End event fires. So I thought I would write a post on the same.

While thinking of Session_End event one of the most important things is that the event is supported only when the session is maintained Inproc. The session_End event will not fire if you are using State server or SQL server.

Another important point to note is that Session_End event is fired by a worker process. This also means that Session_End event might not have all the permission that a normal page request has. So if you are trying to connect to the SQL server with Windows account, Session_End event might not have required permission, although you can connect to the SQL in Session_Start event.

Now when does the Session_End event fires?

Session_End will fire after a given amount of time where session has been inactive. The given time can be changed globally in the web.config file with the time out attribute or for individual session with the help of Session.Timeout property.

Session_End will also fire when someone calls the Session.Abondon method. Note that the Session_End event will not fire immediately. As said before the Session_End event is fired from worker process. Hence the session ID will also be same.

Remember the Session_End event will not fire in case the user closes the browser. HTTP is a stateless protocol. There is no way for the server to understand that the browser has been closed.

Also another very important thing to note here is that if you do not save anything in the session the Session_End event will not fire. There must be something saved in the session atleast once for the Session_End event to fire.

This also means that if you save something in the session in the first request and abandon the session in the same request the Sesison_End event will not fire, as there was nothing saved in the session ever.

Vikram

Feedback

vikram
Posted on 10/8/2007 5:43:35 AM

Thanks for details of session state ,its really interesting

Vikram
Posted on 6/30/2008 3:13:37 AM

Hi Vikrant,

There is no other easy solution for this. And you should not worry about the size of the file. while moving the file. The size will slow the process only while copying and not while moving the file. Moving the file will not be effected by the size of the file as the windows just changes the memory loaction and does not fully move the file.

ali
Posted on 9/23/2009 9:16:21 AM

thanks

manmohan mundhra
Posted on 2/24/2010 12:45:18 PM

If i set session timeout to 1 minute then session_end will be fired exactally 1 minute. This can be done by calling session.abandon.

Manu
Posted on 10/5/2010 11:18:49 AM

hi vikram,
Is there any way to clear session if user close browser ?
the session is maintained Inproc.

Manu
Posted on 10/5/2010 11:20:51 AM

hi vikram,
Is there any way to clear session if user close browser ?
the session is maintained Inproc.

Nagnath Kendre
Posted on 2/24/2011 2:44:28 PM

NICE POST VIKRAM...

Please post your comments:

Name:  
Email (optional): Your email address will not be posted.
URL (optional):
Comments: HTML will be ignored, URLs will be converted to hyperlinks  
Enter the text you see in the box:
 

Copyright © 2006 - 2012 Vikram Lakhotia