Asp.Net Programming :: Session Timeout Problem


	Session Timeout Problem The web.config in my asp.net application, running on Server2003, has this entry: <sessionState mode="InProc" timeout="40". In IIS the asp.net State Management timeout setting is 40 for my website. In IIS the virtual directory configuration setting is set to 40. The application still timesout at 20 minutes. What else can I do? -- Regards, Gary Blakely set the timeout on page load, see if that helps. -- Regards, Alvin Bruney ------------------------------------------------------ Shameless author plug Excel Services for .NET is coming... https://www.microsoft.com/MSPress/books/10933.aspx OWC Black Book www.lulu.com/owc Professional VSTO 2005 - Wrox/Wiley "GaryDean" <GaryD@newsgroups.nospam> wrote in message news:eGW681xoHHA.3952@TK2MSFTNGP03.phx.gbl... - Hide quoted text - > The web.config in my asp.net application, running on Server2003, has this > entry: <sessionState mode="InProc" timeout="40". > In IIS the asp.net State Management timeout setting is 40 for my website. > In IIS the virtual directory configuration setting is set to 40. > The application still timesout at 20 minutes. > What else can I do? > -- > Regards, > Gary Blakely you probably have asp.net configured to shutdown after 20 mins of idle. this causes a recycle which loses all session data. if you use inproc session, you will sometimes lose session data due to a recycle, so your site should be coded to handle this case. -- bruce (sqlwork.com) - Hide quoted text - GaryDean wrote: > The web.config in my asp.net application, running on Server2003, has this > entry: <sessionState mode="InProc" timeout="40". > In IIS the asp.net State Management timeout setting is 40 for my website. > In IIS the virtual directory configuration setting is set to 40. > The application still timesout at 20 minutes. > What else can I do? Hi Gary, As you mentioned that you've used three session setting, then what's the actual session mode you use now, inproc one? I suggeset you create a simplified application and use inproc session to verify the behavior. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights. -----------------------------------------------Reply----------------------------------------------- Could you be a little more specific? I have asp.net configured to shutdown after 20 mins? where? how? "site should be coded to handle this case? how? -- Regards, Gary Blakely "bruce barker" <nos@nospam.com> wrote in message news:uu3mkp0oHHA.4428@TK2MSFTNGP06.phx.gbl... - Hide quoted text - > you probably have asp.net configured to shutdown after 20 mins of idle. > this causes a recycle which loses all session data. > if you use inproc session, you will sometimes lose session data due to a > recycle, so your site should be coded to handle this case. > -- bruce (sqlwork.com) > GaryDean wrote: >> The web.config in my asp.net application, running on Server2003, has this >> entry: <sessionState mode="InProc" timeout="40". >> In IIS the asp.net State Management timeout setting is 40 for my website. >> In IIS the virtual directory configuration setting is set to 40. >> The application still timesout at 20 minutes. >> What else can I do? Steven, you ask "what's the actual session mode you use now" not sure I understand your question. In my original post I stated the session settings in my web.config and the setting is IIS. every conceivable setting I know of says 40 minutes but the application timesout after 20 minutes. -- Regards, Gary Blakely "Steven Cheng[MSFT]" <stch@online.microsoft.com> wrote in message news:MZ4C1f2oHHA.5420@TK2MSFTNGHUB02.phx.gbl... - Hide quoted text - > Hi Gary, > As you mentioned that you've used three session setting, then what's the > actual session mode you use now, inproc one? I suggeset you create a > simplified application and use inproc session to verify the behavior. > Sincerely, > Steven Cheng > Microsoft MSDN Online Support Lead > This posting is provided "AS IS" with no warranties, and confers no > rights. re: !> every conceivable setting I know of says !> 40 minutes but the application timesout after 20 minutes. Including the Forms Authentication timeout ( if you're using that ? ). That defaults to 20 minutes, too. Juan T. Llibre, asp.net MVP asp.net faq : http://asp.net.do/faq/ foros de asp.net, en espaol : http://asp.net.do/foros/ ====================================== "GaryDean" <GaryD@newsgroups.nospam> wrote in message news:O$Ty6z5oHHA.4632@TK2MSFTNGP04.phx.gbl... - Hide quoted text - > Steven, > you ask "what's the actual session mode you use now" not sure I understand your question. In my > original post I stated the session settings in my web.config and the setting is IIS. every > conceivable setting I know of says 40 minutes but the application timesout after 20 minutes. > -- > Regards, > Gary Blakely > "Steven Cheng[MSFT]" <stch@online.microsoft.com> wrote in message > news:MZ4C1f2oHHA.5420@TK2MSFTNGHUB02.phx.gbl... >> Hi Gary, >> As you mentioned that you've used three session setting, then what's the >> actual session mode you use now, inproc one? I suggeset you create a >> simplified application and use inproc session to verify the behavior. >> Sincerely, >> Steven Cheng >> Microsoft MSDN Online Support Lead >> This posting is provided "AS IS" with no warranties, and confers no rights. re: !> I have asp.net configured to shutdown after 20 mins? where? how? 20 minutes is the default. If you don't have a timeout configured...you'll get a 20 minute timeout. To get back to the problem, are you using Forms Authentication ? Could that be set to 20 minutes ? Juan T. Llibre, asp.net MVP asp.net faq : http://asp.net.do/faq/ foros de asp.net, en espaol : http://asp.net.do/foros/ ====================================== "GaryDean" <GaryD@newsgroups.nospam> wrote in message news:%23S0Hsu5oHHA.4772@TK2MSFTNGP05.phx.gbl... - Hide quoted text - > Could you be a little more specific? > I have asp.net configured to shutdown after 20 mins? where? how? > "site should be coded to handle this case? how? > -- > Regards, > Gary Blakely > "bruce barker" <nos@nospam.com> wrote in message news:uu3mkp0oHHA.4428@TK2MSFTNGP06.phx.gbl... >> you probably have asp.net configured to shutdown after 20 mins of idle. this causes a recycle >> which loses all session data. >> if you use inproc session, you will sometimes lose session data due to a recycle, so your site >> should be coded to handle this case. >> -- bruce (sqlwork.com) >> GaryDean wrote: >>> The web.config in my asp.net application, running on Server2003, has this entry: <sessionState >>> mode="InProc" timeout="40". >>> In IIS the asp.net State Management timeout setting is 40 for my website. >>> In IIS the virtual directory configuration setting is set to 40. >>> The application still timesout at 20 minutes. >>> What else can I do? I believe that timeout default is 30, but yes I also set the Forms Authentication timout to 40. -- Regards, Gary Blakely "Juan T. Llibre" <nomailrepl@nowhere.com> wrote in message news:%23kALHa6oHHA.716@TK2MSFTNGP05.phx.gbl... - Hide quoted text - > re: > !> every conceivable setting I know of says > !> 40 minutes but the application timesout after 20 minutes. > Including the Forms Authentication timeout ( if you're using that ? ). > That defaults to 20 minutes, too. > Juan T. Llibre, asp.net MVP > asp.net faq : http://asp.net.do/faq/ > foros de asp.net, en espaol : http://asp.net.do/foros/ > ====================================== > "GaryDean" <GaryD@newsgroups.nospam> wrote in message > news:O$Ty6z5oHHA.4632@TK2MSFTNGP04.phx.gbl... >> Steven, >> you ask "what's the actual session mode you use now" not sure I >> understand your question. In my original post I stated the session >> settings in my web.config and the setting is IIS. every conceivable >> setting I know of says 40 minutes but the application timesout after 20 >> minutes. >> -- >> Regards, >> Gary Blakely >> "Steven Cheng[MSFT]" <stch@online.microsoft.com> wrote in message >> news:MZ4C1f2oHHA.5420@TK2MSFTNGHUB02.phx.gbl... >>> Hi Gary, >>> As you mentioned that you've used three session setting, then what's the >>> actual session mode you use now, inproc one? I suggeset you create a >>> simplified application and use inproc session to verify the behavior. >>> Sincerely, >>> Steven Cheng >>> Microsoft MSDN Online Support Lead >>> This posting is provided "AS IS" with no warranties, and confers no >>> rights. If you have set all the timeouts to 40, and the app is still losing the session variables at 20, then either the app is recycling at 20 or the application pool is recycling at 20. Have you attempted to set a different recycling threshold in the IIS Manager ? Also, have you tried to use State Server, instead of InProc ? State Server, as does SQL Server, gets around the loss of session variables due to Application/App Pool recycling. Juan T. Llibre, asp.net MVP asp.net faq : http://asp.net.do/faq/ foros de asp.net, en espaol : http://asp.net.do/foros/ ====================================== "GaryDean" <GaryD@newsgroups.nospam> wrote in message news:ebilfd%23oHHA.3252@TK2MSFTNGP05.phx.gbl... - Hide quoted text - >I believe that timeout default is 30, but yes I also set the Forms Authentication timout to 40. > -- > Regards, > Gary Blakely > "Juan T. Llibre" <nomailrepl@nowhere.com> wrote in message > news:%23kALHa6oHHA.716@TK2MSFTNGP05.phx.gbl... >> re: >> !> every conceivable setting I know of says >> !> 40 minutes but the application timesout after 20 minutes. >> Including the Forms Authentication timeout ( if you're using that ? ). >> That defaults to 20 minutes, too. >> Juan T. Llibre, asp.net MVP >> asp.net faq : http://asp.net.do/faq/ >> foros de asp.net, en espaol : http://asp.net.do/foros/ >> ====================================== >> "GaryDean" <GaryD@newsgroups.nospam> wrote in message >> news:O$Ty6z5oHHA.4632@TK2MSFTNGP04.phx.gbl... >>> Steven, >>> you ask "what's the actual session mode you use now" not sure I understand your question. In >>> my original post I stated the session settings in my web.config and the setting is IIS. every >>> conceivable setting I know of says 40 minutes but the application timesout after 20 minutes. >>> -- >>> Regards, >>> Gary Blakely >>> "Steven Cheng[MSFT]" <stch@online.microsoft.com> wrote in message >>> news:MZ4C1f2oHHA.5420@TK2MSFTNGHUB02.phx.gbl... >>>> Hi Gary, >>>> As you mentioned that you've used three session setting, then what's the >>>> actual session mode you use now, inproc one? I suggeset you create a >>>> simplified application and use inproc session to verify the behavior. >>>> Sincerely, >>>> Steven Cheng >>>> Microsoft MSDN Online Support Lead >>>> This posting is provided "AS IS" with no warranties, and confers no rights. I've goolged and looked everywhere I can and I can't find anything on "recycling threshold settings" in IIS. My original question at the beginning of this thread stands. -- Regards, Gary Blakely "Juan T. Llibre" <nomailrepl@nowhere.com> wrote in message news:OOIkr6%23oHHA.3772@TK2MSFTNGP03.phx.gbl... - Hide quoted text - > If you have set all the timeouts to 40, and the app is still losing the > session variables > at 20, then either the app is recycling at 20 or the application pool is > recycling at 20. > Have you attempted to set a different recycling threshold in the IIS > Manager ? > Also, have you tried to use State Server, instead of InProc ? > State Server, as does SQL Server, gets around the loss of > session variables due to Application/App Pool recycling. > Juan T. Llibre, asp.net MVP > asp.net faq : http://asp.net.do/faq/ > foros de asp.net, en espaol : http://asp.net.do/foros/ > ====================================== > "GaryDean" <GaryD@newsgroups.nospam> wrote in message > news:ebilfd%23oHHA.3252@TK2MSFTNGP05.phx.gbl... >>I believe that timeout default is 30, but yes I also set the Forms >>Authentication timout to 40. >> -- >> Regards, >> Gary Blakely >> "Juan T. Llibre" <nomailrepl@nowhere.com> wrote in message >> news:%23kALHa6oHHA.716@TK2MSFTNGP05.phx.gbl... >>> re: >>> !> every conceivable setting I know of says >>> !> 40 minutes but the application timesout after 20 minutes. >>> Including the Forms Authentication timeout ( if you're using that ? ). >>> That defaults to 20 minutes, too. >>> Juan T. Llibre, asp.net MVP >>> asp.net faq : http://asp.net.do/faq/ >>> foros de asp.net, en espaol : http://asp.net.do/foros/ >>> ====================================== >>> "GaryDean" <GaryD@newsgroups.nospam> wrote in message >>> news:O$Ty6z5oHHA.4632@TK2MSFTNGP04.phx.gbl... >>>> Steven, >>>> you ask "what's the actual session mode you use now" not sure I >>>> understand your question. In my original post I stated the session >>>> settings in my web.config and the setting is IIS. every conceivable >>>> setting I know of says 40 minutes but the application timesout after 20 >>>> minutes. >>>> -- >>>> Regards, >>>> Gary Blakely >>>> "Steven Cheng[MSFT]" <stch@online.microsoft.com> wrote in message >>>> news:MZ4C1f2oHHA.5420@TK2MSFTNGHUB02.phx.gbl... >>>>> Hi Gary, >>>>> As you mentioned that you've used three session setting, then what's >>>>> the >>>>> actual session mode you use now, inproc one? I suggeset you create a >>>>> simplified application and use inproc session to verify the behavior. >>>>> Sincerely, >>>>> Steven Cheng >>>>> Microsoft MSDN Online Support Lead >>>>> This posting is provided "AS IS" with no warranties, and confers no >>>>> rights. no, it's set to 40. Everythingis set to 40. -- Regards, Gary Blakely "Juan T. Llibre" <nomailrepl@nowhere.com> wrote in message news:%23Kz5eZ6oHHA.1476@TK2MSFTNGP03.phx.gbl... - Hide quoted text - > re: > !> I have asp.net configured to shutdown after 20 mins? where? how? > 20 minutes is the default. > If you don't have a timeout configured...you'll get a 20 minute timeout. > To get back to the problem, are you using Forms Authentication ? > Could that be set to 20 minutes ? > Juan T. Llibre, asp.net MVP > asp.net faq : http://asp.net.do/faq/ > foros de asp.net, en espaol : http://asp.net.do/foros/ > ====================================== > "GaryDean" <GaryD@newsgroups.nospam> wrote in message > news:%23S0Hsu5oHHA.4772@TK2MSFTNGP05.phx.gbl... >> Could you be a little more specific? >> I have asp.net configured to shutdown after 20 mins? where? how? >> "site should be coded to handle this case? how? >> -- >> Regards, >> Gary Blakely >> "bruce barker" <nos@nospam.com> wrote in message >> news:uu3mkp0oHHA.4428@TK2MSFTNGP06.phx.gbl... >>> you probably have asp.net configured to shutdown after 20 mins of idle. >>> this causes a recycle which loses all session data. >>> if you use inproc session, you will sometimes lose session data due to a >>> recycle, so your site should be coded to handle this case. >>> -- bruce (sqlwork.com) >>> GaryDean wrote: >>>> The web.config in my asp.net application, running on Server2003, has >>>> this entry: <sessionState mode="InProc" timeout="40". >>>> In IIS the asp.net State Management timeout setting is 40 for my >>>> website. >>>> In IIS the virtual directory configuration setting is set to 40. >>>> The application still timesout at 20 minutes. >>>> What else can I do? In Windows Server 2003, you can set the recycling threshhold for the Application Pool in which an application runs. In the IIS Manager, scroll down the left hand panel to "Application Pools", and select the Application Pool in which your app runs. Right-click the App Pool and select "Properties" from the context menu. You'll see several options for setting the time/memory limit/number of requests at which the application pool will be recycled. Just make sure your time setting isn't set too low. Leave the rest untouched until you are familiar with the settings. You don't say whether you tried using State Server. !> Also, have you tried to use State Server, instead of InProc state management? !> State Server state management, as does SQL Server, gets around !> the loss of session variables due to Application/App Pool recycling. Just configure it in web.config : <sessionState mode="StateServer" stateConnectionString="tcpip=127.0.0.1:42424" stateNetworkTimeout="10" cookieless="false" timeout="20" /> ...and in the "Services" applet of the W2K3 Server, start the State Server service. That usually works to prevent Session variable losses. Juan T. Llibre, asp.net MVP asp.net faq : http://asp.net.do/faq/ foros de asp.net, en espaol : http://asp.net.do/foros/ ====================================== "GaryDean" <GaryD@newsgroups.nospam> wrote in message news:eYHlPVKpHHA.4032@TK2MSFTNGP02.phx.gbl... - Hide quoted text - > I've goolged and looked everywhere I can and I can't find anything on "recycling threshold > settings" in IIS. My original question at the beginning of this thread stands. > -- > Regards, > Gary Blakely > "Juan T. Llibre" <nomailrepl@nowhere.com> wrote in message > news:OOIkr6%23oHHA.3772@TK2MSFTNGP03.phx.gbl... >> If you have set all the timeouts to 40, and the app is still losing the session variables >> at 20, then either the app is recycling at 20 or the application pool is recycling at 20. >> Have you attempted to set a different recycling threshold in the IIS Manager ? >> Also, have you tried to use State Server, instead of InProc ? >> State Server, as does SQL Server, gets around the loss of >> session variables due to Application/App Pool recycling. >> Juan T. Llibre, asp.net MVP >> asp.net faq : http://asp.net.do/faq/ >> foros de asp.net, en espaol : http://asp.net.do/foros/ >> ====================================== >> "GaryDean" <GaryD@newsgroups.nospam> wrote in message >> news:ebilfd%23oHHA.3252@TK2MSFTNGP05.phx.gbl... >>>I believe that timeout default is 30, but yes I also set the Forms Authentication timout to 40. >>> -- >>> Regards, >>> Gary Blakely >>> "Juan T. Llibre" <nomailrepl@nowhere.com> wrote in message >>> news:%23kALHa6oHHA.716@TK2MSFTNGP05.phx.gbl... >>>> re: >>>> !> every conceivable setting I know of says >>>> !> 40 minutes but the application timesout after 20 minutes. >>>> Including the Forms Authentication timeout ( if you're using that ? ). >>>> That defaults to 20 minutes, too. >>>> Juan T. Llibre, asp.net MVP >>>> asp.net faq : http://asp.net.do/faq/ >>>> foros de asp.net, en espaol : http://asp.net.do/foros/ >>>> ====================================== >>>> "GaryDean" <GaryD@newsgroups.nospam> wrote in message >>>> news:O$Ty6z5oHHA.4632@TK2MSFTNGP04.phx.gbl... >>>>> Steven, >>>>> you ask "what's the actual session mode you use now" not sure I understand your question. In >>>>> my original post I stated the session settings in my web.config and the setting is IIS. every >>>>> conceivable setting I know of says 40 minutes but the application timesout after 20 minutes. >>>>> -- >>>>> Regards, >>>>> Gary Blakely >>>>> "Steven Cheng[MSFT]" <stch@online.microsoft.com> wrote in message >>>>> news:MZ4C1f2oHHA.5420@TK2MSFTNGHUB02.phx.gbl... >>>>>> Hi Gary, >>>>>> As you mentioned that you've used three session setting, then what's the >>>>>> actual session mode you use now, inproc one? I suggeset you create a >>>>>> simplified application and use inproc session to verify the behavior. >>>>>> Sincerely, >>>>>> Steven Cheng >>>>>> Microsoft MSDN Online Support Lead >>>>>> This posting is provided "AS IS" with no warranties, and confers no rights. Juan, That was it. The other settings had already extended my Session.timeout but then we were getting null session variables after 20 minutes. I didn't try State Server because we just don't need it now for this low-arrival rate app. Thank you very much for your help on this issue. Regards, Gary Blakely "Juan T. Llibre" <nomailrepl@nowhere.com> wrote in message news:eln9gOLpHHA.3320@TK2MSFTNGP05.phx.gbl... - Hide quoted text - > In Windows Server 2003, you can set the recycling threshhold > for the Application Pool in which an application runs. > In the IIS Manager, scroll down the left hand panel to "Application > Pools", > and select the Application Pool in which your app runs. > Right-click the App Pool and select "Properties" from the context menu. > You'll see several options for setting the time/memory limit/number of > requests > at which the application pool will be recycled. > Just make sure your time setting isn't set too low. > Leave the rest untouched until you are familiar with the settings. > You don't say whether you tried using State Server. > !> Also, have you tried to use State Server, instead of InProc state > management? > !> State Server state management, as does SQL Server, gets around > !> the loss of session variables due to Application/App Pool recycling. > Just configure it in web.config : > <sessionState > mode="StateServer" > stateConnectionString="tcpip=127.0.0.1:42424" > stateNetworkTimeout="10" > cookieless="false" > timeout="20" > /> > ...and in the "Services" applet of the W2K3 Server, start the State Server > service. > That usually works to prevent Session variable losses. > Juan T. Llibre, asp.net MVP > asp.net faq : http://asp.net.do/faq/ > foros de asp.net, en espaol : http://asp.net.do/foros/ > ====================================== > "GaryDean" <GaryD@newsgroups.nospam> wrote in message > news:eYHlPVKpHHA.4032@TK2MSFTNGP02.phx.gbl... >> I've goolged and looked everywhere I can and I can't find anything on >> "recycling threshold settings" in IIS. My original question at the >> beginning of this thread stands. >> -- >> Regards, >> Gary Blakely >> "Juan T. Llibre" <nomailrepl@nowhere.com> wrote in message >> news:OOIkr6%23oHHA.3772@TK2MSFTNGP03.phx.gbl... >>> If you have set all the timeouts to 40, and the app is still losing the >>> session variables >>> at 20, then either the app is recycling at 20 or the application pool is >>> recycling at 20. >>> Have you attempted to set a different recycling threshold in the IIS >>> Manager ? >>> Also, have you tried to use State Server, instead of InProc ? >>> State Server, as does SQL Server, gets around the loss of >>> session variables due to Application/App Pool recycling. >>> Juan T. Llibre, asp.net MVP >>> asp.net faq : http://asp.net.do/faq/ >>> foros de asp.net, en espaol : http://asp.net.do/foros/ >>> ====================================== >>> "GaryDean" <GaryD@newsgroups.nospam> wrote in message >>> news:ebilfd%23oHHA.3252@TK2MSFTNGP05.phx.gbl... >>>>I believe that timeout default is 30, but yes I also set the Forms >>>>Authentication timout to 40. >>>> -- >>>> Regards, >>>> Gary Blakely >>>> "Juan T. Llibre" <nomailrepl@nowhere.com> wrote in message >>>> news:%23kALHa6oHHA.716@TK2MSFTNGP05.phx.gbl... >>>>> re: >>>>> !> every conceivable setting I know of says >>>>> !> 40 minutes but the application timesout after 20 minutes. >>>>> Including the Forms Authentication timeout ( if you're using that ? ). >>>>> That defaults to 20 minutes, too. >>>>> Juan T. Llibre, asp.net MVP >>>>> asp.net faq : http://asp.net.do/faq/ >>>>> foros de asp.net, en espaol : http://asp.net.do/foros/ >>>>> ====================================== >>>>> "GaryDean" <GaryD@newsgroups.nospam> wrote in message >>>>> news:O$Ty6z5oHHA.4632@TK2MSFTNGP04.phx.gbl... >>>>>> Steven, >>>>>> you ask "what's the actual session mode you use now" not sure I >>>>>> understand your question. In my original post I stated the session >>>>>> settings in my web.config and the setting is IIS. every conceivable >>>>>> setting I know of says 40 minutes but the application timesout after >>>>>> 20 minutes. >>>>>> -- >>>>>> Regards, >>>>>> Gary Blakely >>>>>> "Steven Cheng[MSFT]" <stch@online.microsoft.com> wrote in message >>>>>> news:MZ4C1f2oHHA.5420@TK2MSFTNGHUB02.phx.gbl... >>>>>>> Hi Gary, >>>>>>> As you mentioned that you've used three session setting, then what's >>>>>>> the >>>>>>> actual session mode you use now, inproc one? I suggeset you create >>>>>>> a >>>>>>> simplified application and use inproc session to verify the >>>>>>> behavior. >>>>>>> Sincerely, >>>>>>> Steven Cheng >>>>>>> Microsoft MSDN Online Support Lead >>>>>>> This posting is provided "AS IS" with no warranties, and confers no >>>>>>> rights. re: !> Juan, !> That was it. Glad to hear that! re: !> Thank you very much for your help on this issue. You're quite welcome. Glad to know you're up and running trouble-free again. Juan T. Llibre, asp.net MVP asp.net faq : http://asp.net.do/faq/ foros de asp.net, en espaol : http://asp.net.do/foros/ ====================================== "GaryDean" <GaryD@newsgroups.nospam> wrote in message news:%23XcsAPgpHHA.4032@TK2MSFTNGP02.phx.gbl... - Hide quoted text - > Juan, > That was it. The other settings had already extended my Session.timeout but then we were getting > null session variables after 20 minutes. I didn't try State Server because we just don't need it > now for this low-arrival rate app. > Thank you very much for your help on this issue. > Regards, > Gary Blakely > "Juan T. Llibre" <nomailrepl@nowhere.com> wrote in message > news:eln9gOLpHHA.3320@TK2MSFTNGP05.phx.gbl... >> In Windows Server 2003, you can set the recycling threshhold >> for the Application Pool in which an application runs. >> In the IIS Manager, scroll down the left hand panel to "Application Pools", >> and select the Application Pool in which your app runs. >> Right-click the App Pool and select "Properties" from the context menu. >> You'll see several options for setting the time/memory limit/number of requests >> at which the application pool will be recycled. >> Just make sure your time setting isn't set too low. >> Leave the rest untouched until you are familiar with the settings. >> You don't say whether you tried using State Server. >> !> Also, have you tried to use State Server, instead of InProc state management? >> !> State Server state management, as does SQL Server, gets around >> !> the loss of session variables due to Application/App Pool recycling. >> Just configure it in web.config : >> <sessionState >> mode="StateServer" >> stateConnectionString="tcpip=127.0.0.1:42424" >> stateNetworkTimeout="10" >> cookieless="false" >> timeout="20" >> /> >> ...and in the "Services" applet of the W2K3 Server, start the State Server service. >> That usually works to prevent Session variable losses. >> Juan T. Llibre, asp.net MVP >> asp.net faq : http://asp.net.do/faq/ >> foros de asp.net, en espaol : http://asp.net.do/foros/ >> ====================================== >> "GaryDean" <GaryD@newsgroups.nospam> wrote in message >> news:eYHlPVKpHHA.4032@TK2MSFTNGP02.phx.gbl... >>> I've goolged and looked everywhere I can and I can't find anything on "recycling threshold >>> settings" in IIS. My original question at the beginning of this thread stands. >>> -- >>> Regards, >>> Gary Blakely >>> "Juan T. Llibre" <nomailrepl@nowhere.com> wrote in message >>> news:OOIkr6%23oHHA.3772@TK2MSFTNGP03.phx.gbl... >>>> If you have set all the timeouts to 40, and the app is still losing the session variables >>>> at 20, then either the app is recycling at 20 or the application pool is recycling at 20. >>>> Have you attempted to set a different recycling threshold in the IIS Manager ? >>>> Also, have you tried to use State Server, instead of InProc ? >>>> State Server, as does SQL Server, gets around the loss of >>>> session variables due to Application/App Pool recycling. >>>> Juan T. Llibre, asp.net MVP >>>> asp.net faq : http://asp.net.do/faq/ >>>> foros de asp.net, en espaol : http://asp.net.do/foros/ >>>> ====================================== >>>> "GaryDean" <GaryD@newsgroups.nospam> wrote in message >>>> news:ebilfd%23oHHA.3252@TK2MSFTNGP05.phx.gbl... >>>>>I believe that timeout default is 30, but yes I also set the Forms Authentication timout to 40. >>>>> -- >>>>> Regards, >>>>> Gary Blakely >>>>> "Juan T. Llibre" <nomailrepl@nowhere.com> wrote in message >>>>> news:%23kALHa6oHHA.716@TK2MSFTNGP05.phx.gbl... >>>>>> re: >>>>>> !> every conceivable setting I know of says >>>>>> !> 40 minutes but the application timesout after 20 minutes. >>>>>> Including the Forms Authentication timeout ( if you're using that ? ). >>>>>> That defaults to 20 minutes, too. >>>>>> Juan T. Llibre, asp.net MVP >>>>>> asp.net faq : http://asp.net.do/faq/ >>>>>> foros de asp.net, en espaol : http://asp.net.do/foros/ >>>>>> ====================================== >>>>>> "GaryDean" <GaryD@newsgroups.nospam> wrote in message >>>>>> news:O$Ty6z5oHHA.4632@TK2MSFTNGP04.phx.gbl... >>>>>>> Steven, >>>>>>> you ask "what's the actual session mode you use now" not sure I understand your question. >>>>>>> In my original post I stated the session settings in my web.config and the setting is IIS. >>>>>>> every conceivable setting I know of says 40 minutes but the application timesout after 20 >>>>>>> minutes. >>>>>>> -- >>>>>>> Regards, >>>>>>> Gary Blakely >>>>>>> "Steven Cheng[MSFT]" <stch@online.microsoft.com> wrote in message >>>>>>> news:MZ4C1f2oHHA.5420@TK2MSFTNGHUB02.phx.gbl... >>>>>>>> Hi Gary, >>>>>>>> As you mentioned that you've used three session setting, then what's the >>>>>>>> actual session mode you use now, inproc one? I suggeset you create a >>>>>>>> simplified application and use inproc session to verify the behavior. >>>>>>>> Sincerely, >>>>>>>> Steven Cheng >>>>>>>> Microsoft MSDN Online Support Lead >>>>>>>> This posting is provided "AS IS" with no warranties, and confers no rights.