Re: How long can my asp.net application run for?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Thanks for the suggestion!

In my web.config for my Visual Studio project I modified the timout
attribute as follows:
<sessionState
mode="InProc"
stateConnectionString="tcpip=127.0.0.1:42424"
sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes"
cookieless="false"
timeout="240"
/>

Also, in IIS Manager I right clicked on the folder in which my application
lives, went to properties, on the Directory tab I clicked on the
Configuration button, went to the options tab and changed the Session timeout
from the default 20 to 240.

Rebuilt my application, restarted IIS and ran my application again. I still
didn't make it past the ~25 min mark, and got the same page cannot be
displayed error.

In an attempt to troubleshoot what might be causing the problem I added code
in my global.asax.cs to write a text file with the system time in it for the
following events:
Application_Start
Session_Start
Session_End
Application_End

After running the application, only one file was written: Application_Start
(which leads me to believe the session_start/end and application_end events
never occured).

Any other ideas?

Thanks all for your time!

- Chase


"Clamps" wrote:

> Have a look at session.timeout
>
>
> "Chase" <Chase@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:3044B711-D67D-4986-8DA7-CBECC330D9B3@xxxxxxxxxxxxxxxx
> > I'm pretty new to asp.net and am having problems with my application
> timing
> > out.
> >
> > I've written an application that loops through all of the information on
> an
> > excel spread*** and does certain things with it, like creating and
> > configuring WSS sites.
> >
> > My application runs fine for approximately 25 minutes, then I get the
> 'Page
> > cannot be displayed' error. It seems like my browser times out before the
> > application can finish what its doing.
> >
> > What settings should I be checking? Are there asp.net settings I need to
> > configure, or is my browser the culprit (does it think the page is never
> > going to load and just time out)?
> >
> > Thanks for any help!
> >
> > - Chase
>
>
>
.

Quantcast