Sessions Expiring Prematurely on Production

[Andrew Chung]

Hi all,

For an application that I'm working on, upon successful
authentication, Session.Timeout is set to 60 minutes. This behaviour
works as expected on my own machine. If I refresh a page after 40
minutes of inactivity, it remains, but after 61 minutes, it expires
and I am sent back to the login page.

However, once this code is put on the Production server, the sessions
time out after only 20 minutes, even though the code sets it to 60.
What could be causing this? The application is compiled before being
put on Production, in case that matters.

Thanks.

[Teemu Keiski]

In case sessions are set to use in-Proc mode, there can be various reasons
why it expires. AppDomain restarts would cause sessions to expire, and
AppDomain restart can happen when web.config is modified, bin folder
modified, or multiple files / directories are created etc etc, it can even
be a virus scanner touching some files.

See following posts for further information:
http://blogs.msdn.com/tess/archive/2...s.aspx#1572598

http://weblogs.asp.net/scottgu/archi...14/433194.aspx
--
Teemu Keiski
AspInsider, ASP.NET MVP
http://blogs.aspadvice.com/joteke
http://teemukeiski.net


"Andrew Chung" <az***********@gmail.comwrote in message
news:11**********************@h3g2000cwc.googlegro ups.com...

Hi all,

For an application that I'm working on, upon successful
authentication, Session.Timeout is set to 60 minutes. This behaviour
works as expected on my own machine. If I refresh a page after 40
minutes of inactivity, it remains, but after 61 minutes, it expires
and I am sent back to the login page.

However, once this code is put on the Production server, the sessions
time out after only 20 minutes, even though the code sets it to 60.
What could be causing this? The application is compiled before being
put on Production, in case that matters.

Thanks.

[=?Utf-8?B?UGV0ZXIgQnJvbWJlcmcgW0MjIE1WUF0=?=]

In addition to what Teemu has said, are you sure that it's the Session timing
out and not the fact that the Forms Authentication Ticket may have expired?
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Andrew Chung" wrote:

Hi all,

For an application that I'm working on, upon successful
authentication, Session.Timeout is set to 60 minutes. This behaviour
works as expected on my own machine. If I refresh a page after 40
minutes of inactivity, it remains, but after 61 minutes, it expires
and I am sent back to the login page.

However, once this code is put on the Production server, the sessions
time out after only 20 minutes, even though the code sets it to 60.
What could be causing this? The application is compiled before being
put on Production, in case that matters.

Thanks.

[Andrew Chung]

On Feb 12, 12:01 pm, Peter Bromberg [C# MVP]
<[e-mail]:

In addition to what Teemu has said, are you sure that it's the Session timing
out and not the fact that the Forms Authentication Ticket may have expired?
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net

"Andrew Chung" wrote:

Hi all,

For an application that I'm working on, upon successful
authentication, Session.Timeout is set to 60 minutes. This behaviour
works as expected on my own machine. If I refresh a page after 40
minutes of inactivity, it remains, but after 61 minutes, it expires
and I am sent back to the login page.

However, once this code is put on the Production server, the sessions
time out after only 20 minutes, even though the code sets it to 60.
What could be causing this? The application is compiled before being
put on Production, in case that matters.

Thanks.

I'm not using Forms Authentication, the Authentication is done
manually.

[Andrew Chung]

On Feb 12, 12:01 pm, Peter Bromberg [C# MVP]
<[e-mail]:

In addition to what Teemu has said, are you sure that it's the Session timing
out and not the fact that the Forms Authentication Ticket may have expired?
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net

"Andrew Chung" wrote:

Hi all,

For an application that I'm working on, upon successful
authentication, Session.Timeout is set to 60 minutes. This behaviour
works as expected on my own machine. If I refresh a page after 40
minutes of inactivity, it remains, but after 61 minutes, it expires
and I am sent back to the login page.

However, once this code is put on the Production server, the sessions
time out after only 20 minutes, even though the code sets it to 60.
What could be causing this? The application is compiled before being
put on Production, in case that matters.

Thanks.

The authentication is done manually, Form Authentication is not used.

[Andrew Chung]

On Feb 12, 1:29 pm, "Andrew Chung" <[e-mail]:

On Feb 12, 12:01 pm, Peter Bromberg [C# MVP]

<[e-mail]:

In addition to what Teemu has said, are you sure that it's the Session timing
out and not the fact that the Forms Authentication Ticket may have expired?
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net

"Andrew Chung" wrote:

Hi all,

For an application that I'm working on, upon successful
authentication, Session.Timeout is set to 60 minutes. This behaviour
works as expected on my own machine. If I refresh a page after 40
minutes of inactivity, it remains, but after 61 minutes, it expires
and I am sent back to the login page.

However, once this code is put on the Production server, the sessions
time out after only 20 minutes, even though the code sets it to 60.
What could be causing this? The application is compiled before being
put on Production, in case that matters.

Thanks.

The authentication is done manually, Form Authentication is not used.

Oops, didn't know there was a delay in postings, thought I lost them.

[=?Utf-8?B?UGV0ZXIgQnJvbWJlcmcgW0MjIE1WUF0=?=]

Do I hear an echo? Then follow Teemu' advice and links carefully.
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Andrew Chung" wrote:

On Feb 12, 1:29 pm, "Andrew Chung" <[e-mail]:

On Feb 12, 12:01 pm, Peter Bromberg [C# MVP]

<[e-mail]:

In addition to what Teemu has said, are you sure that it's the Session timing
out and not the fact that the Forms Authentication Ticket may have expired?
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net

"Andrew Chung" wrote:
Hi all,

For an application that I'm working on, upon successful
authentication, Session.Timeout is set to 60 minutes. This behaviour
works as expected on my own machine. If I refresh a page after 40
minutes of inactivity, it remains, but after 61 minutes, it expires
and I am sent back to the login page.

However, once this code is put on the Production server, the sessions
time out after only 20 minutes, even though the code sets it to 60.
What could be causing this? The application is compiled before being
put on Production, in case that matters.

Thanks.

The authentication is done manually, Form Authentication is not used.

Oops, didn't know there was a delay in postings, thought I lost them.