Re: Sessions timing out quickly despite very high timeout set in web.config
- From: "Juan T. Llibre" <nomailreplies@xxxxxxxxxxx>
- Date: Fri, 24 Aug 2007 15:04:14 -0400
You might want to look into what is causing your applications to recycle.
An easy way to do this is to implement Scott Guthrie's
tips for logging ASP.NET application shutdown events :
http://weblogs.asp.net/scottgu/archive/2005/12/14/433194.aspx
By using this diagnostics tool, you can figure out why and when ASP.NET restarts application domains.
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
======================================
"Alex" <samalex@xxxxxxxxx> wrote in message news:%237gBphn5HHA.1212@xxxxxxxxxxxxxxxxxxxxxxx
Hello,
We have a large asp.net writtin in VB.Net 2003, and for some reason the sessions have started timing out very quickly,
like 5-10 minutes in some cases. In web.config we have the SessionState timeout set at 720 minutes, but this doesn't
seem to help.
What we're seeing is users working in the system just fine, then they'll get the following error when the application
tries to reference the session:
-[Begin Snippet]-------------------------------------
Server Error in '/' Application.
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack
trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin
and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.]
Sigma.DetailsReport.RetrieveData() in C:\Inetpub\wwwroot\App\Loan\Details.aspx.vb:107
Sigma.DetailsReport.Page_Load(Object sender, EventArgs e) in C:\Inetpub\wwwroot\App\Loan\Details.aspx.vb:71
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +750
Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300
-[End Snippet]-------------------------------------
When reviewing the code from the trace, it always is something that references something in the Session, and my
assumption is the session has expired causing a null to be returned.
I'm fairly new to the world of VB, but being a seasoned web coder of other languages I'm not sure exactly what to try
next. I'm working on adding code to detect the timeout and return something other then a .Net error, but this still
won't help the fact that our sessions are timing out in a matter of minutes when they shouldn't be.
Thanks in advance for any advise or suggestions on this --
Alex
.
- References:
- Prev by Date: Re: [Global.asax] how to manage two or more of them?
- Next by Date: Re: Sessions timing out quickly despite very high timeout set in web.config
- Previous by thread: Re: Sessions timing out quickly despite very high timeout set in web.config
- Next by thread: Body.Attributes.Add
- Index(es):
Relevant Pages
|
