Session Timeouts

I have developed an asp.net 2.0 app on my instance of server2003 and have
set IIS to timout in 40 minutes (asp.net|configuration) and it works just
fine - the app won't timeout until 40 minutes of inactivity passes.
However when deployed to a production server2003 machine with the very same
IIS settings, the app times out in 20 minutes. I have no specific timeout
statement either in code or web.config.
Any ideas?
Regards,
Gary BlakelyOn May 25, 6:48 am, "GaryDean" <GaryD...@.newsgroups.nospam> wrote:
> I have developed an asp.net 2.0 app on my instance of server2003 and have
> set IIS to timout in 40 minutes (asp.net|configuration) and it works just
> fine - the app won't timeout until 40 minutes of inactivity passes.
> However when deployed to a production server2003 machine with the very sam
e
> IIS settings, the app times out in 20 minutes. I have no specific timeout
> statement either in code or web.config.
> Any ideas?
> --
> Regards,
> Gary Blakely
Hi Gary...
20 min is a default timeout period...
please add timeout configuration in web.config and set it to 40 min...
if this problem still remains please check your machine.config
file...
Thanks
Masudur
I guess I failed to say that I have tried all of the obvious solutions, some
of which, you suggest.
Regards,
Gary Blakely
"Masudur" <munnacs@.gmail.com> wrote in message
news:1180069599.240101.129060@.g4g2000hsf.googlegroups.com...
> On May 25, 6:48 am, "GaryDean" <GaryD...@.newsgroups.nospam> wrote:
> Hi Gary...
> 20 min is a default timeout period...
> please add timeout configuration in web.config and set it to 40 min...
> if this problem still remains please check your machine.config
> file...
> Thanks
> Masudur
>
On May 27, 6:53 pm, "GaryDean" <GaryD...@.newsgroups.nospam> wrote:
> I guess I failed to say that I have tried all of the obvious solutions, so
me
> of which, you suggest.
>
So, did you tried to set timeout in the web.config file?
<sessionState mode="InProc"
cookieless="true"
timeout="40"/>
Hi Gary,
This issue does look strange, if you're pretty sure that the obvious
web.config settings and IIS settings are correctly configured:
1) web.config, see Alexey's suggestion.
2) IIS: virtual directory properties -> (Directory) Configuration ->
(Options) "Session timeout".
Maybe we're lack of some context or background information, would you
please depict more on the other configuration settings your web site
having? Thanks.
Regards,
Walter Wang (wawang@.online.microsoft.com, remove 'online.')
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
Walter,
Is there some reason cookieless="true" has to be coupled with the timeout
setting?
BTW, are there any downsides to cookieless sessions other than having the
sessionID in the url?
Regards,
Gary Blakely
"Walter Wang [MSFT]" <wawang@.online.microsoft.com> wrote in message
news:3X3TzCZoHHA.1144@.TK2MSFTNGHUB02.phx.gbl...
> Hi Gary,
> This issue does look strange, if you're pretty sure that the obvious
> web.config settings and IIS settings are correctly configured:
> 1) web.config, see Alexey's suggestion.
> 2) IIS: virtual directory properties -> (Directory) Configuration ->
> (Options) "Session timeout".
>
> Maybe we're lack of some context or background information, would you
> please depict more on the other configuration settings your web site
> having? Thanks.
>
> Regards,
> Walter Wang (wawang@.online.microsoft.com, remove 'online.')
> Microsoft Online Community Support
> ========================================
==========
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
==========
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
also, this is a little strange...
if iis is set to 20 and my web.config says timeout="40" at 22 minutes of no
activity the user does not get the login screen, the session variables are
just null.
Regards,
Gary Blakely
"Walter Wang [MSFT]" <wawang@.online.microsoft.com> wrote in message
news:3X3TzCZoHHA.1144@.TK2MSFTNGHUB02.phx.gbl...
> Hi Gary,
> This issue does look strange, if you're pretty sure that the obvious
> web.config settings and IIS settings are correctly configured:
> 1) web.config, see Alexey's suggestion.
> 2) IIS: virtual directory properties -> (Directory) Configuration ->
> (Options) "Session timeout".
>
> Maybe we're lack of some context or background information, would you
> please depict more on the other configuration settings your web site
> having? Thanks.
>
> Regards,
> Walter Wang (wawang@.online.microsoft.com, remove 'online.')
> Microsoft Online Community Support
> ========================================
==========
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
==========
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
I have new information and I am going to start a new thread on this
Regards,
Gary Blakely
"Walter Wang [MSFT]" <wawang@.online.microsoft.com> wrote in message
news:3X3TzCZoHHA.1144@.TK2MSFTNGHUB02.phx.gbl...
> Hi Gary,
> This issue does look strange, if you're pretty sure that the obvious
> web.config settings and IIS settings are correctly configured:
> 1) web.config, see Alexey's suggestion.
> 2) IIS: virtual directory properties -> (Directory) Configuration ->
> (Options) "Session timeout".
>
> Maybe we're lack of some context or background information, would you
> please depict more on the other configuration settings your web site
> having? Thanks.
>
> Regards,
> Walter Wang (wawang@.online.microsoft.com, remove 'online.')
> Microsoft Online Community Support
> ========================================
==========
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
==========
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>

Session Timeouts

I have developed an asp.net 2.0 app on my instance of server2003 and have
set IIS to timout in 40 minutes (asp.net|configuration) and it works just
fine - the app won't timeout until 40 minutes of inactivity passes.

However when deployed to a production server2003 machine with the very same
IIS settings, the app times out in 20 minutes. I have no specific timeout
statement either in code or web.config.

Any ideas?

--
Regards,
Gary BlakelyOn May 25, 6:48 am, "GaryDean" <GaryD...@.newsgroups.nospamwrote:

Quote:

Originally Posted by

I have developed an asp.net 2.0 app on my instance of server2003 and have
set IIS to timout in 40 minutes (asp.net|configuration) and it works just
fine - the app won't timeout until 40 minutes of inactivity passes.
>
However when deployed to a production server2003 machine with the very same
IIS settings, the app times out in 20 minutes. I have no specific timeout
statement either in code or web.config.
>
Any ideas?
>
--
Regards,
Gary Blakely

Hi Gary...

20 min is a default timeout period...
please add timeout configuration in web.config and set it to 40 min...
if this problem still remains please check your machine.config
file...

Thanks
Masudur
I guess I failed to say that I have tried all of the obvious solutions, some
of which, you suggest.

--
Regards,
Gary Blakely
"Masudur" <munnacs@.gmail.comwrote in message
news:1180069599.240101.129060@.g4g2000hsf.googlegro ups.com...

Quote:

Originally Posted by

On May 25, 6:48 am, "GaryDean" <GaryD...@.newsgroups.nospamwrote:

Quote:

Originally Posted by

>I have developed an asp.net 2.0 app on my instance of server2003 and have
>set IIS to timout in 40 minutes (asp.net|configuration) and it works just
>fine - the app won't timeout until 40 minutes of inactivity passes.
>>
>However when deployed to a production server2003 machine with the very
>same
>IIS settings, the app times out in 20 minutes. I have no specific
>timeout
>statement either in code or web.config.
>>
>Any ideas?
>>
>--
>Regards,
>Gary Blakely

>
Hi Gary...
>
20 min is a default timeout period...
please add timeout configuration in web.config and set it to 40 min...
if this problem still remains please check your machine.config
file...
>
Thanks
Masudur
>

On May 27, 6:53 pm, "GaryDean" <GaryD...@.newsgroups.nospamwrote:

Quote:

Originally Posted by

I guess I failed to say that I have tried all of the obvious solutions, some
of which, you suggest.
>

So, did you tried to set timeout in the web.config file?

<sessionState mode="InProc"
cookieless="true"
timeout="40"/>
Hi Gary,

This issue does look strange, if you're pretty sure that the obvious
web.config settings and IIS settings are correctly configured:

1) web.config, see Alexey's suggestion.

2) IIS: virtual directory properties -(Directory) Configuration ->
(Options) "Session timeout".

Maybe we're lack of some context or background information, would you
please depict more on the other configuration settings your web site
having? Thanks.

Regards,
Walter Wang (wawang@.online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
Walter,
Is there some reason cookieless="true" has to be coupled with the timeout
setting?

BTW, are there any downsides to cookieless sessions other than having the
sessionID in the url?

--
Regards,
Gary Blakely
"Walter Wang [MSFT]" <wawang@.online.microsoft.comwrote in message
news:3X3TzCZoHHA.1144@.TK2MSFTNGHUB02.phx.gbl...

Quote:

Originally Posted by

Hi Gary,
>
This issue does look strange, if you're pretty sure that the obvious
web.config settings and IIS settings are correctly configured:
>
1) web.config, see Alexey's suggestion.
>
2) IIS: virtual directory properties -(Directory) Configuration ->
(Options) "Session timeout".
>
>
Maybe we're lack of some context or background information, would you
please depict more on the other configuration settings your web site
having? Thanks.
>
>
Regards,
Walter Wang (wawang@.online.microsoft.com, remove 'online.')
Microsoft Online Community Support
>
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
>
This posting is provided "AS IS" with no warranties, and confers no
rights.
>

also, this is a little strange...
if iis is set to 20 and my web.config says timeout="40" at 22 minutes of no
activity the user does not get the login screen, the session variables are
just null.

--
Regards,
Gary Blakely

"Walter Wang [MSFT]" <wawang@.online.microsoft.comwrote in message
news:3X3TzCZoHHA.1144@.TK2MSFTNGHUB02.phx.gbl...

Quote:

Originally Posted by

Hi Gary,
>
This issue does look strange, if you're pretty sure that the obvious
web.config settings and IIS settings are correctly configured:
>
1) web.config, see Alexey's suggestion.
>
2) IIS: virtual directory properties -(Directory) Configuration ->
(Options) "Session timeout".
>
>
Maybe we're lack of some context or background information, would you
please depict more on the other configuration settings your web site
having? Thanks.
>
>
Regards,
Walter Wang (wawang@.online.microsoft.com, remove 'online.')
Microsoft Online Community Support
>
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
>
This posting is provided "AS IS" with no warranties, and confers no
rights.
>

I have new information and I am going to start a new thread on this

--
Regards,
Gary Blakely
"Walter Wang [MSFT]" <wawang@.online.microsoft.comwrote in message
news:3X3TzCZoHHA.1144@.TK2MSFTNGHUB02.phx.gbl...

Quote:

Originally Posted by

Hi Gary,
>
This issue does look strange, if you're pretty sure that the obvious
web.config settings and IIS settings are correctly configured:
>
1) web.config, see Alexey's suggestion.
>
2) IIS: virtual directory properties -(Directory) Configuration ->
(Options) "Session timeout".
>
>
Maybe we're lack of some context or background information, would you
please depict more on the other configuration settings your web site
having? Thanks.
>
>
Regards,
Walter Wang (wawang@.online.microsoft.com, remove 'online.')
Microsoft Online Community Support
>
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
>
This posting is provided "AS IS" with no warranties, and confers no
rights.
>

Session variables disappear

Hi all,

We have a small problem.

We are running an ASP.NET1.1 application, using IIS6 on server2003, no web
farm, on a single server, using in-proc session state, only using one worker
process.

The problem is that at seemingly random times, some of the session variables
return as if set to nothing.

We are using session variables to pass small objects from one page request
to the next. Which seems to work perfectly most of the time, but as I said
above, at random times, some but not all of the session variables return as
nothing.

Anyone any ideas?

Thanks in advance and Regards,
Simon.This is hard to diagnose without a lot of context information, but here is a
suggestion:

Try switching to cookieless for a while and see if the problem persists. If
not, then it may be some sort of cookie issue. The only other thing to be
aware of is that IIS process recycling will force you to lose session state.
The IIS settings on that may be too aggressive.
Peter
--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com

"Simon" wrote:

> Hi all,
> We have a small problem.
> We are running an ASP.NET1.1 application, using IIS6 on server2003, no web
> farm, on a single server, using in-proc session state, only using one worker
> process.
> The problem is that at seemingly random times, some of the session variables
> return as if set to nothing.
> We are using session variables to pass small objects from one page request
> to the next. Which seems to work perfectly most of the time, but as I said
> above, at random times, some but not all of the session variables return as
> nothing.
> Anyone any ideas?
> Thanks in advance and Regards,
> Simon.
>
check the event log for asp.net recycles - these will clear inproc sessions.
(real production servers should not use inproc sessions for this reason)

-- bruce (sqlwork.com)

"Simon" <s@.v.c> wrote in message
news:43e8835f$0$82636$ed2619ec@.ptn-nntp-reader03.plus.net...
> Hi all,
> We have a small problem.
> We are running an ASP.NET1.1 application, using IIS6 on server2003, no web
> farm, on a single server, using in-proc session state, only using one
> worker process.
> The problem is that at seemingly random times, some of the session
> variables return as if set to nothing.
> We are using session variables to pass small objects from one page request
> to the next. Which seems to work perfectly most of the time, but as I said
> above, at random times, some but not all of the session variables return
> as nothing.
> Anyone any ideas?
> Thanks in advance and Regards,
> Simon.
You can use performance monitor to see how often .NET application restarts.
When it does so all sessions are lost.

Couple reasons why application would restart.

1. new version of DLL was uploaded into BIN folder.
2. More than 15 aspx files were updated/added (15 is configurable value but
by default it's 15).
3. Folder in the project directory was created/removed.
4. There is antivirus active on the machine. Although it will not modify
aspx files it will trigger same sequence as it would. (See #2)
5. The application hanged or reached it's memory limit.

Also check eventlog there might be something in there especially if you have
case #5.

George.

"Simon" <s@.v.c> wrote in message
news:43e8835f$0$82636$ed2619ec@.ptn-nntp-reader03.plus.net...
> Hi all,
> We have a small problem.
> We are running an ASP.NET1.1 application, using IIS6 on server2003, no web
> farm, on a single server, using in-proc session state, only using one
> worker process.
> The problem is that at seemingly random times, some of the session
> variables return as if set to nothing.
> We are using session variables to pass small objects from one page request
> to the next. Which seems to work perfectly most of the time, but as I said
> above, at random times, some but not all of the session variables return
> as nothing.
> Anyone any ideas?
> Thanks in advance and Regards,
> Simon.
Thanks for the reply,

What would you suggest we use instead of inproc.
We have looked at sqlserver, but all objects that you put in session must be
serializable, which some of them aren't

Thanks,
Simon.

"Bruce Barker" <brubar_nospamplease_@.safeco.com> wrote in message
news:%23uIZxwBLGHA.3064@.TK2MSFTNGP10.phx.gbl...
> check the event log for asp.net recycles - these will clear inproc
> sessions. (real production servers should not use inproc sessions for this
> reason)
> -- bruce (sqlwork.com)
> "Simon" <s@.v.c> wrote in message
> news:43e8835f$0$82636$ed2619ec@.ptn-nntp-reader03.plus.net...
>> Hi all,
>>
>> We have a small problem.
>>
>> We are running an ASP.NET1.1 application, using IIS6 on server2003, no
>> web farm, on a single server, using in-proc session state, only using one
>> worker process.
>>
>> The problem is that at seemingly random times, some of the session
>> variables return as if set to nothing.
>>
>> We are using session variables to pass small objects from one page
>> request to the next. Which seems to work perfectly most of the time, but
>> as I said above, at random times, some but not all of the session
>> variables return as nothing.
>>
>> Anyone any ideas?
>>
>> Thanks in advance and Regards,
>> Simon.
>>
Thanks for the reply George,

Surely if the application restarts, then all current sessions will end and
all session variables will disappear which we test for at the start of each
page load.

The problems occur after it has already returned several session items, and
then one of them comes back as nothing.

Perhaps the application is restarting mid request? is that possible? or is
it possible that objects can get GC'd when in session?

Regards,
Simon.

"George Ter-Saakov" <gt-nsp@.cardone.com> wrote in message
news:OToPtBCLGHA.536@.TK2MSFTNGP09.phx.gbl...
> You can use performance monitor to see how often .NET application
> restarts.
> When it does so all sessions are lost.
> Couple reasons why application would restart.
> 1. new version of DLL was uploaded into BIN folder.
> 2. More than 15 aspx files were updated/added (15 is configurable value
> but by default it's 15).
> 3. Folder in the project directory was created/removed.
> 4. There is antivirus active on the machine. Although it will not modify
> aspx files it will trigger same sequence as it would. (See #2)
> 5. The application hanged or reached it's memory limit.
> Also check eventlog there might be something in there especially if you
> have case #5.
>
>
> George.
>
> "Simon" <s@.v.c> wrote in message
> news:43e8835f$0$82636$ed2619ec@.ptn-nntp-reader03.plus.net...
>> Hi all,
>>
>> We have a small problem.
>>
>> We are running an ASP.NET1.1 application, using IIS6 on server2003, no
>> web farm, on a single server, using in-proc session state, only using one
>> worker process.
>>
>> The problem is that at seemingly random times, some of the session
>> variables return as if set to nothing.
>>
>> We are using session variables to pass small objects from one page
>> request to the next. Which seems to work perfectly most of the time, but
>> as I said above, at random times, some but not all of the session
>> variables return as nothing.
>>
>> Anyone any ideas?
>>
>> Thanks in advance and Regards,
>> Simon.
>>

Session variables disappear

Hi all,
We have a small problem.
We are running an ASP.NET1.1 application, using IIS6 on server2003, no web
farm, on a single server, using in-proc session state, only using one worker
process.
The problem is that at seemingly random times, some of the session variables
return as if set to nothing.
We are using session variables to pass small objects from one page request
to the next. Which seems to work perfectly most of the time, but as I said
above, at random times, some but not all of the session variables return as
nothing.
Anyone any ideas?
Thanks in advance and Regards,
Simon.This is hard to diagnose without a lot of context information, but here is a
suggestion:
Try switching to cookieless for a while and see if the problem persists. If
not, then it may be some sort of cookie issue. The only other thing to be
aware of is that IIS process recycling will force you to lose session state.
The IIS settings on that may be too aggressive.
Peter
--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
"Simon" wrote:

> Hi all,
> We have a small problem.
> We are running an ASP.NET1.1 application, using IIS6 on server2003, no web
> farm, on a single server, using in-proc session state, only using one work
er
> process.
> The problem is that at seemingly random times, some of the session variabl
es
> return as if set to nothing.
> We are using session variables to pass small objects from one page request
> to the next. Which seems to work perfectly most of the time, but as I said
> above, at random times, some but not all of the session variables return a
s
> nothing.
> Anyone any ideas?
> Thanks in advance and Regards,
> Simon.
>
>
check the event log for asp.net recycles - these will clear inproc sessions.
(real production servers should not use inproc sessions for this reason)
-- bruce (sqlwork.com)
"Simon" <s@.v.c> wrote in message
news:43e8835f$0$82636$ed2619ec@.ptn-nntp-reader03.plus.net...
> Hi all,
> We have a small problem.
> We are running an ASP.NET1.1 application, using IIS6 on server2003, no web
> farm, on a single server, using in-proc session state, only using one
> worker process.
> The problem is that at seemingly random times, some of the session
> variables return as if set to nothing.
> We are using session variables to pass small objects from one page request
> to the next. Which seems to work perfectly most of the time, but as I said
> above, at random times, some but not all of the session variables return
> as nothing.
> Anyone any ideas?
> Thanks in advance and Regards,
> Simon.
>
You can use performance monitor to see how often .NET application restarts.
When it does so all sessions are lost.
Couple reasons why application would restart.
1. new version of DLL was uploaded into BIN folder.
2. More than 15 aspx files were updated/added (15 is configurable value but
by default it's 15).
3. Folder in the project directory was created/removed.
4. There is antivirus active on the machine. Although it will not modify
aspx files it will trigger same sequence as it would. (See #2)
5. The application hanged or reached it's memory limit.
Also check eventlog there might be something in there especially if you have
case #5.
George.
"Simon" <s@.v.c> wrote in message
news:43e8835f$0$82636$ed2619ec@.ptn-nntp-reader03.plus.net...
> Hi all,
> We have a small problem.
> We are running an ASP.NET1.1 application, using IIS6 on server2003, no web
> farm, on a single server, using in-proc session state, only using one
> worker process.
> The problem is that at seemingly random times, some of the session
> variables return as if set to nothing.
> We are using session variables to pass small objects from one page request
> to the next. Which seems to work perfectly most of the time, but as I said
> above, at random times, some but not all of the session variables return
> as nothing.
> Anyone any ideas?
> Thanks in advance and Regards,
> Simon.
>
Thanks for the reply,
What would you suggest we use instead of inproc.
We have looked at sqlserver, but all objects that you put in session must be
serializable, which some of them aren't
Thanks,
Simon.
"Bruce Barker" <brubar_nospamplease_@.safeco.com> wrote in message
news:%23uIZxwBLGHA.3064@.TK2MSFTNGP10.phx.gbl...
> check the event log for asp.net recycles - these will clear inproc
> sessions. (real production servers should not use inproc sessions for this
> reason)
> -- bruce (sqlwork.com)
> "Simon" <s@.v.c> wrote in message
> news:43e8835f$0$82636$ed2619ec@.ptn-nntp-reader03.plus.net...
>
Thanks for the reply George,
Surely if the application restarts, then all current sessions will end and
all session variables will disappear which we test for at the start of each
page load.
The problems occur after it has already returned several session items, and
then one of them comes back as nothing.
Perhaps the application is restarting mid request? is that possible? or is
it possible that objects can get GC'd when in session?
Regards,
Simon.
"George Ter-Saakov" <gt-nsp@.cardone.com> wrote in message
news:OToPtBCLGHA.536@.TK2MSFTNGP09.phx.gbl...
> You can use performance monitor to see how often .NET application
> restarts.
> When it does so all sessions are lost.
> Couple reasons why application would restart.
> 1. new version of DLL was uploaded into BIN folder.
> 2. More than 15 aspx files were updated/added (15 is configurable value
> but by default it's 15).
> 3. Folder in the project directory was created/removed.
> 4. There is antivirus active on the machine. Although it will not modify
> aspx files it will trigger same sequence as it would. (See #2)
> 5. The application hanged or reached it's memory limit.
> Also check eventlog there might be something in there especially if you
> have case #5.
>
>
> George.
>
> "Simon" <s@.v.c> wrote in message
> news:43e8835f$0$82636$ed2619ec@.ptn-nntp-reader03.plus.net...
>