ASP.Net 2.0 Unexpected Session Timeout

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Jack

    ASP.Net 2.0 Unexpected Session Timeout

    We running an ASP.Net 2.0 app on IIS 6. We're trying to set a session
    timeout to 4 hours (business requirement). We've tried setting the timeout
    at login via code, setting it in the global.asax, and setting it in the
    web.config. We still get random timeouts, sometimes less than 5 minutes
    after login.

    We're logging pages that have had their session variables cleared in the
    event logs, and it's on multiple pages. It's like something is recycling
    the worker process, but I don't know why it would.

    Any ideas?


  • bruce barker

    #2
    Re: ASP.Net 2.0 Unexpected Session Timeout

    you need to set the asp.net idle time to more than 4 hours, so automatic
    recycles don't happen. then you need to check the event logs to se how
    often and you are getting recycles (too much memory, file/dir changes, etc).

    -- bruce (sqlwork.com)



    Jack wrote:
    We running an ASP.Net 2.0 app on IIS 6. We're trying to set a session
    timeout to 4 hours (business requirement). We've tried setting the timeout
    at login via code, setting it in the global.asax, and setting it in the
    web.config. We still get random timeouts, sometimes less than 5 minutes
    after login.
    >
    We're logging pages that have had their session variables cleared in the
    event logs, and it's on multiple pages. It's like something is recycling
    the worker process, but I don't know why it would.
    >
    Any ideas?
    >
    >

    Comment

    • mark4asp

      #3
      Re: ASP.Net 2.0 Unexpected Session Timeout

      On Fri, 13 Jul 2007 15:45:12 -0400, "Brian Simmons"
      <centraso@newsg roup.nospamwrot e:
      >Just let him be, and if you don't have a solution or suggestion to his
      >specific problem, let it be. Keep your personal agenda to yourself.
      Kevin is trying to give someone best long term advice which I think is
      better than just giving the punter a piece of Elastoplast.
      >Perhaps his application is used solely by the CEO of the company, and the
      >CEO has personally requested a 4 hour timeout. The CEO signs his paycheck,
      >you don't think the original poster is going to do everything within his
      >power to meet the CEO demands.
      Sometimes you need to have the balls to look the CEO in the face and
      tell them they're wrong and they can't do that - and maybe even hint
      that you'll leave if they continue interfering in matters that are
      beyond their ken.

      Comment

      • Juan T. Llibre

        #4
        Re: ASP.Net 2.0 Unexpected Session Timeout

        Could you consider not using Sessions at all and, instead
        implementing a Forms-based authentication scheme
        whose timeout you can set to any length of time you want to ?





        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/
        =============== =============== ========
        "Jack" <anonymous@micr osoft.comwrote in message news:OddJhgWxHH A.3560@TK2MSFTN GP02.phx.gbl...
        We running an ASP.Net 2.0 app on IIS 6. We're trying to set a session timeout to 4 hours (business requirement).
        We've tried setting the timeout at login via code, setting it in the global.asax, and setting it in the web.config.
        We still get random timeouts, sometimes less than 5 minutes after login.
        We're logging pages that have had their session variables cleared in the event logs, and it's on multiple pages. It's
        like something is recycling the worker process, but I don't know why it would.
        Any ideas?

        Comment

        Working...