Session Timeout using frames

Hello,

My main ASP.NET interface uses frames. The problem is that once the session
times out (if the user hasn't yet closed the browser), the user is
automatically redirected to the login screen (setup in Web.Config file), but
this occurs for every frame!!! Is there a way to redirect away from the main
interface completely?

Thanks!your frame page is html or aspx?
if it is html try to rename in aspx!

"Bilbo" <Bilbo@.cox.net> wrote in message
news:OSWo03XVEHA.1652@.TK2MSFTNGP09.phx.gbl...
> Hello,
> My main ASP.NET interface uses frames. The problem is that once the
session
> times out (if the user hasn't yet closed the browser), the user is
> automatically redirected to the login screen (setup in Web.Config file),
but
> this occurs for every frame!!! Is there a way to redirect away from the
main
> interface completely?
> Thanks!
Its kinda irritating but I found a solution for it.
Use this javascript so the login page will "bust out of frame".

<script>
if (parent.frames.length > 0) {
parent.location.href = self.document.location
}
</script
This script make sure that the page will bust out of frame, so you only have
one login page.

Richard

"Bilbo" <Bilbo@.cox.net> schreef in bericht
news:OSWo03XVEHA.1652@.TK2MSFTNGP09.phx.gbl...
> Hello,
> My main ASP.NET interface uses frames. The problem is that once the
session
> times out (if the user hasn't yet closed the browser), the user is
> automatically redirected to the login screen (setup in Web.Config file),
but
> this occurs for every frame!!! Is there a way to redirect away from the
main
> interface completely?
> Thanks!
In the Login Page add this Client Side Code so that you can "Break Away
From Frames"

<Script Language="JavaScript">
if (top != self) {top.location.href = self.location.href;}
</Script --
Trevor Benedict R
MCSD

*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!

Session Timeout setting in IIS.

IIS has a Session Timeout setting. How does this setting coincide with the
ASP.NET property Session.SessionTimeout value. If I change this value in
code, will it override the IIS Session Timeout setting?
--
Ken Varn
Senior Software Engineer
Diebold Inc.
EmailID = varnk
Domain = Diebold.com
--Hi,
IIS's session settings affect only classic ASP etc, not ASP.NET's and vice
versa (with ASP.NET/Framework 2.0 you get ASP.NET tab on IIS where you can
manage config file settings, those do have affect on ASP.NET but of course
not on classic ASP)
Teemu Keiski
ASP.NET MVP, AspInsider
Finland, EU
http://blogs.aspadvice.com/joteke
"Ken Varn" <nospam> wrote in message
news:eOGLehIkGHA.1296@.TK2MSFTNGP05.phx.gbl...
> IIS has a Session Timeout setting. How does this setting coincide with
> the
> ASP.NET property Session.SessionTimeout value. If I change this value in
> code, will it override the IIS Session Timeout setting?
> --
> --
> Ken Varn
> Senior Software Engineer
> Diebold Inc.
> EmailID = varnk
> Domain = Diebold.com
> --
>

Session Timeout setting in IIS.

IIS has a Session Timeout setting. How does this setting coincide with the
ASP.NET property Session.SessionTimeout value. If I change this value in
code, will it override the IIS Session Timeout setting?

--
-----------
Ken Varn
Senior Software Engineer
Diebold Inc.

EmailID = varnk
Domain = Diebold.com
-----------Hi,

IIS's session settings affect only classic ASP etc, not ASP.NET's and vice
versa (with ASP.NET/Framework 2.0 you get ASP.NET tab on IIS where you can
manage config file settings, those do have affect on ASP.NET but of course
not on classic ASP)

--
Teemu Keiski
ASP.NET MVP, AspInsider
Finland, EU
http://blogs.aspadvice.com/joteke

"Ken Varn" <nospam> wrote in message
news:eOGLehIkGHA.1296@.TK2MSFTNGP05.phx.gbl...
> IIS has a Session Timeout setting. How does this setting coincide with
> the
> ASP.NET property Session.SessionTimeout value. If I change this value in
> code, will it override the IIS Session Timeout setting?
> --
> -----------
> Ken Varn
> Senior Software Engineer
> Diebold Inc.
> EmailID = varnk
> Domain = Diebold.com
> -----------

Session time-out,when the page breaks?

Hi..

I had published a website in the server( I am using VS 2005,ASP.NET2.0, With C#) . I tried testing the site by asking several users to login to the website and do unit testing. At one instance of time, the page breaks for a particular user. When the page breaks, the other users who are tesing in their machine are getting a session time-out and are forced to log out.

Why is such a session-time out issue happening, when one of the users page breaks. I have set the session variable to 20 minutes,which is the default. But what's confusing is , when one of the user's page breaks, the others get a session time-out? Why is such a session-time out occuring?

Please help.

Thanks.

What do you mean when you say "the page breaks?" If an app pool cycles you might see this effect. Have you diagnosed the "page break" to see what happens?

Jeff

Thank you very much for the reply.

The page break, I referred is the page crashing(asp.net error page) .I have customized the error page to show, An Unexpected error occurred, please try after some time.

But when the user tries the same steps to find the page crash, he is not able to, as the page works well. This is a kind of absurd. The page is not crashing always, but it is random. I checked the log, but it was not providing much information. I also could not re-trace the page crash, as the page worked well.

But why is the session getting timed out for the other users, when one of the users page crashes?

Thanks.

Hi..

I am sorry that I forgot to include a scenario in my web page,which i am doing. I have written a code to delete a folder in the session end in global.asax. When i commented the code, and tried testing, the session time out was not occuring.

I searched in the google, and came out with this:

http://www.velocityreviews.com/forums/t116975-all-session-are-getting-down-when-i-delete-sessions-folders.html

Is this the reason for all sessions getting timed-out, when a page crashes?

Thanks

Hi Venkatzeus,

As far as i know, if you delete a folder which is in your application directory, the appDomain will restart, and you will lose your session.

I hope this helps.

This happens as your worker process memory limits get full and asp.net worker process gets restarted. how to do this setting you can find at

http://www.asp.net/faq/AspNetAndIIS6.aspx

But I think you needs to findout why its getting full.

When you get this error check server CPU Usage what it shows?

then debug.

HI,,

Thank you very much for the reply. I will try with it and provide the results.

Thanks

Session Timeout, not working

I have set the session timeout something greater then 20 minutes in
the web.config(120 minutes for testing) after 20 minutes to 30 minutes
click a button and am redirected back to the login. My Session is
reporting 120 minutes I know this becuase I display on a debug page.
below are the 2 areas in the web.config that I set anybody tell me
whats wrong or what is missing.
<sessionState mode="InProc" regenerateExpiredSessionId="false"
timeout="120">
</sessionState>
<forms name=".GSNAUTH" loginUrl="Login.aspx" path="/"
protection="Encryption" timeout="120" slidingExpiration="true"/>
When previeing on the page I see the top 1 becuase I have been able
to adjust it down to 60 minutes or 35 minutes whatever.
When I display on the debug page I show
lblSessionTimeout.text = Session.Timeout;
NOt sure what I am missing."Scott" <sremiger@.groceryshopping.net> wrote in message
news:47b0bb72-a003-4f59-9e19-fb5cbe61e720@.o77g2000hsf.googlegroups.com...
> I have set the session timeout something greater then 20 minutes in
> the web.config(120 minutes for testing) after 20 minutes to 30 minutes
> click a button and am redirected back to the login. My Session is
> reporting 120 minutes I know this becuase I display on a debug page.
> below are the 2 areas in the web.config that I set anybody tell me
> whats wrong or what is missing.
> <sessionState mode="InProc" regenerateExpiredSessionId="false"
> timeout="120">
> </sessionState>
> <forms name=".GSNAUTH" loginUrl="Login.aspx" path="/"
> protection="Encryption" timeout="120" slidingExpiration="true"/>
> When previeing on the page I see the top 1 becuase I have been able
> to adjust it down to 60 minutes or 35 minutes whatever.
> When I display on the debug page I show
> lblSessionTimeout.text = Session.Timeout;
> NOt sure what I am missing.
Unless you have other clients creating activity on the site your Application
Pool is probably timing out. When a pool has seen absolutely no activity
whatsoever it can shutdown. Check the settings on the pool to which your
application belongs.
Anthony Jones - MVP ASP/ASP.NET
Session expiration and forms authentication timeouts are two separate and
distinct things. Being redirected to a login page is a forms authentication
timeout issue, unless somehow you are also using session to do this.
Your ASP.NET application can recycle for any number of reasons, and when it
does, all inProc Sessions go bye-bye.
-- Peter
Site: http://www.eggheadcafe.com
UnBlog: htp://petesbloggerama.blogspot.com
Short Urls & more: http://ittyurl.net
"Scott" wrote:

> I have set the session timeout something greater then 20 minutes in
> the web.config(120 minutes for testing) after 20 minutes to 30 minutes
> click a button and am redirected back to the login. My Session is
> reporting 120 minutes I know this becuase I display on a debug page.
> below are the 2 areas in the web.config that I set anybody tell me
> whats wrong or what is missing.
> <sessionState mode="InProc" regenerateExpiredSessionId="false"
> timeout="120">
> </sessionState>
> <forms name=".GSNAUTH" loginUrl="Login.aspx" path="/"
> protection="Encryption" timeout="120" slidingExpiration="true"/>
> When previeing on the page I see the top 1 becuase I have been able
> to adjust it down to 60 minutes or 35 minutes whatever.
> When I display on the debug page I show
> lblSessionTimeout.text = Session.Timeout;
> NOt sure what I am missing.
>

Session Timeout using frames

Hello,
My main ASP.NET interface uses frames. The problem is that once the session
times out (if the user hasn't yet closed the browser), the user is
automatically redirected to the login screen (setup in Web.Config file), but
this occurs for every frame!!! Is there a way to redirect away from the main
interface completely?
Thanks!your frame page is html or aspx?
if it is html try to rename in aspx!
"Bilbo" <Bilbo@.cox.net> wrote in message
news:OSWo03XVEHA.1652@.TK2MSFTNGP09.phx.gbl...
> Hello,
> My main ASP.NET interface uses frames. The problem is that once the
session
> times out (if the user hasn't yet closed the browser), the user is
> automatically redirected to the login screen (setup in Web.Config file),
but
> this occurs for every frame!!! Is there a way to redirect away from the
main
> interface completely?
> Thanks!
>
In the Login Page add this Client Side Code so that you can "Break Away
From Frames"
<Script Language="JavaScript">
if (top != self) {top.location.href = self.location.href;}
</Script -->
Trevor Benedict R
MCSD
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!
Its kinda irritating but I found a solution for it.
Use this javascript so the login page will "bust out of frame".
<script>
if (parent.frames.length > 0) {
parent.location.href = self.document.location
}
</script>
This script make sure that the page will bust out of frame, so you only have
one login page.
Richard
"Bilbo" <Bilbo@.cox.net> schreef in bericht
news:OSWo03XVEHA.1652@.TK2MSFTNGP09.phx.gbl...
> Hello,
> My main ASP.NET interface uses frames. The problem is that once the
session
> times out (if the user hasn't yet closed the browser), the user is
> automatically redirected to the login screen (setup in Web.Config file),
but
> this occurs for every frame!!! Is there a way to redirect away from the
main
> interface completely?
> Thanks!
>

Session Timeout..

When the session times out, I would like to navigate to the login page.
Currently when the session times out, the displayed screen remains visible
on the screen however when the user clicks on the screen will take to the
login page.

How to do that?

BenjaminYou could try using the javascript setTimeout function set to 20 minutes
(the default session timeout period) and then set the
document.location.href='login.aspx' via client side code.
Here's an example of using the javascript setTimeout function:
http://www.crowes.f9.co.uk/Javascript/timer.htm

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net

"Benjamin Smith" <BenSmithNg@.hotmail.com> wrote in message
news:%23%23YjkXrmEHA.3608@.TK2MSFTNGP09.phx.gbl...
> When the session times out, I would like to navigate to the login page.
> Currently when the session times out, the displayed screen remains visible
> on the screen however when the user clicks on the screen will take to the
> login page.
> How to do that?
> Benjamin
Hi i had the same problem.
Buti fixed..
If u need a more detailed script let me know!

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Yes, I need to know.
Benjamin

"naijacoder naijacoder" <naijacoder@.toughguy.net> wrote in message
news:eu0aGPsmEHA.3988@.tk2msftngp13.phx.gbl...
> Hi i had the same problem.
> Buti fixed..
> If u need a more detailed script let me know!
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!
But what do you really want to do?

"Benjamin Smith" <BenSmithNg@.hotmail.com> wrote in message
news:eFTtrasmEHA.2908@.TK2MSFTNGP12.phx.gbl...
> Yes, I need to know.
> Benjamin
> "naijacoder naijacoder" <naijacoder@.toughguy.net> wrote in message
> news:eu0aGPsmEHA.3988@.tk2msftngp13.phx.gbl...
> > Hi i had the same problem.
> > Buti fixed..
> > If u need a more detailed script let me know!
> > *** Sent via Developersdex http://www.developersdex.com ***
> > Don't just participate in USENET...get rewarded for it!
Steve gave you the answer. In more detail:

Session times out (by default) 20 minutes after the last Request was
received by the client browser instance holding that SessionID in a
temporary cookie. As no request is received on the server, no response can
be sent to the client. Therefore, the redirect MUST occur on the client.
That means JavaScript. And that means that your JavaScript function should
fire just as the Session times out (20 minutes). You would use the
JavaScript setTimeOut() function to accomplish this.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
I get paid good money to
solve puzzles for a living

"Benjamin Smith" <BenSmithNg@.hotmail.com> wrote in message
news:eFTtrasmEHA.2908@.TK2MSFTNGP12.phx.gbl...
> Yes, I need to know.
> Benjamin
> "naijacoder naijacoder" <naijacoder@.toughguy.net> wrote in message
> news:eu0aGPsmEHA.3988@.tk2msftngp13.phx.gbl...
> > Hi i had the same problem.
> > Buti fixed..
> > If u need a more detailed script let me know!
> > *** Sent via Developersdex http://www.developersdex.com ***
> > Don't just participate in USENET...get rewarded for it!
Thanks for your answers.

Now I understand I have to use setTimeout to achieve my goal.

The link http://www.crowes.f9.co.uk/Javascript/timer.htm is really helpful.

Which client side event I should use to keep track the user is still using
the website.

Thanks,

Benjamin

"Steve C. Orr [MVP, MCSD]" <Steve@.Orr.net> wrote in message
news:#lv4LermEHA.324@.TK2MSFTNGP11.phx.gbl...
> You could try using the javascript setTimeout function set to 20 minutes
> (the default session timeout period) and then set the
> document.location.href='login.aspx' via client side code.
> Here's an example of using the javascript setTimeout function:
> http://www.crowes.f9.co.uk/Javascript/timer.htm
> --
> I hope this helps,
> Steve C. Orr, MCSD, MVP
> http://Steve.Orr.net
>
> "Benjamin Smith" <BenSmithNg@.hotmail.com> wrote in message
> news:%23%23YjkXrmEHA.3608@.TK2MSFTNGP09.phx.gbl...
> > When the session times out, I would like to navigate to the login page.
> > Currently when the session times out, the displayed screen remains
visible
> > on the screen however when the user clicks on the screen will take to
the
> > login page.
> > How to do that?
> > Benjamin
Also I would like to inform the user just before X seconds of page expiry. I
do not want to use alert(). Is it possible to display the message on the
tool bar as once the count down for expire starts.

Thanks,

Benjamin

"Steve C. Orr [MVP, MCSD]" <Steve@.Orr.net> wrote in message
news:#lv4LermEHA.324@.TK2MSFTNGP11.phx.gbl...
> You could try using the javascript setTimeout function set to 20 minutes
> (the default session timeout period) and then set the
> document.location.href='login.aspx' via client side code.
> Here's an example of using the javascript setTimeout function:
> http://www.crowes.f9.co.uk/Javascript/timer.htm
> --
> I hope this helps,
> Steve C. Orr, MCSD, MVP
> http://Steve.Orr.net
>
> "Benjamin Smith" <BenSmithNg@.hotmail.com> wrote in message
> news:%23%23YjkXrmEHA.3608@.TK2MSFTNGP09.phx.gbl...
> > When the session times out, I would like to navigate to the login page.
> > Currently when the session times out, the displayed screen remains
visible
> > on the screen however when the user clicks on the screen will take to
the
> > login page.
> > How to do that?
> > Benjamin
The browser will keep track of that for you.
All you need is one client side event to fire once the trigger time has
elapsed and you want to warn the user.
You can name the event anything you want.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net

"Benjamin" <BenSmithNg@.hotmail.com> wrote in message
news:uan1PfQnEHA.392@.tk2msftngp13.phx.gbl...
> Thanks for your answers.
> Now I understand I have to use setTimeout to achieve my goal.
> The link http://www.crowes.f9.co.uk/Javascript/timer.htm is really
> helpful.
> Which client side event I should use to keep track the user is still using
> the website.
> Thanks,
> Benjamin
>
> "Steve C. Orr [MVP, MCSD]" <Steve@.Orr.net> wrote in message
> news:#lv4LermEHA.324@.TK2MSFTNGP11.phx.gbl...
>> You could try using the javascript setTimeout function set to 20 minutes
>> (the default session timeout period) and then set the
>> document.location.href='login.aspx' via client side code.
>> Here's an example of using the javascript setTimeout function:
>> http://www.crowes.f9.co.uk/Javascript/timer.htm
>>
>> --
>> I hope this helps,
>> Steve C. Orr, MCSD, MVP
>> http://Steve.Orr.net
>>
>>
>> "Benjamin Smith" <BenSmithNg@.hotmail.com> wrote in message
>> news:%23%23YjkXrmEHA.3608@.TK2MSFTNGP09.phx.gbl...
>> > When the session times out, I would like to navigate to the login page.
>> > Currently when the session times out, the displayed screen remains
> visible
>> > on the screen however when the user clicks on the screen will take to
> the
>> > login page.
>>> > How to do that?
>>> > Benjamin
>>>>
>>
Yes you can display a message to the status bar of the browser.
Here's a nice example:
http://simplythebest.net/scripts/DH...ascript_58.html

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net

"Benjamin" <BenSmithNg@.hotmail.com> wrote in message
news:uGdHQhQnEHA.3520@.TK2MSFTNGP11.phx.gbl...
> Also I would like to inform the user just before X seconds of page expiry.
> I
> do not want to use alert(). Is it possible to display the message on the
> tool bar as once the count down for expire starts.
> Thanks,
> Benjamin
>
> "Steve C. Orr [MVP, MCSD]" <Steve@.Orr.net> wrote in message
> news:#lv4LermEHA.324@.TK2MSFTNGP11.phx.gbl...
>> You could try using the javascript setTimeout function set to 20 minutes
>> (the default session timeout period) and then set the
>> document.location.href='login.aspx' via client side code.
>> Here's an example of using the javascript setTimeout function:
>> http://www.crowes.f9.co.uk/Javascript/timer.htm
>>
>> --
>> I hope this helps,
>> Steve C. Orr, MCSD, MVP
>> http://Steve.Orr.net
>>
>>
>> "Benjamin Smith" <BenSmithNg@.hotmail.com> wrote in message
>> news:%23%23YjkXrmEHA.3608@.TK2MSFTNGP09.phx.gbl...
>> > When the session times out, I would like to navigate to the login page.
>> > Currently when the session times out, the displayed screen remains
> visible
>> > on the screen however when the user clicks on the screen will take to
> the
>> > login page.
>>> > How to do that?
>>> > Benjamin
>>>>
>>

Session Timeout.

Friends,
We have a simple application which has login page, users login to it
and enter their contact details and all other stuff. It is working
fine. Now we have moved to new windows 2003 server. The page works
but it gets refreshed every 5 mintues and goes back to login.aspx page.
How do I fix this.
Thanks for any help.
KAdd this in your Web.config file to elongate Session to 60min for example:
<sessionState cookieless="UseCookies" mode="InProc" timeout="60" />
but add it between
<system.web> </system.web>
--
Bishoy George
bishoy@.bishoy.com
20102550399
"Sai" <kumar877@.gmail.com> wrote in message
news:1145074352.770881.44720@.u72g2000cwu.googlegroups.com...
> Friends,
> We have a simple application which has login page, users login to it
> and enter their contact details and all other stuff. It is working
> fine. Now we have moved to new windows 2003 server. The page works
> but it gets refreshed every 5 mintues and goes back to login.aspx page.
> How do I fix this.
> Thanks for any help.
> K
>
no that did not help. same thing is happening again.
Do you have code in your page to redirect to your login page? Sounds like
your session is timing out and your code is kicking in to repost. Write some
code in your session_end event handler to dump a file with a time-stamp to
tell you when the session is dying. You can trouble-shoot from there.
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]
[Shameless Author plug]
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Professional VSTO.NET - Wrox/Wiley 2006
----
"Sai" <kumar877@.gmail.com> wrote in message
news:1145116360.101576.258960@.i40g2000cwc.googlegroups.com...
> no that did not help. same thing is happening again.
>
Hi Alvin,
thanks for the advise. Iam inputting the values to a text file when
session times out. It is coming as 60 seconds. So the session is
timing out at every 60 seconds, but I could not find where to change
these value. I checked the web.config and machine.config and
application pools .
Let me know specific place to change this value.
thanks,
K
So you have an override somewhere in your code because the timeout value is
20 minutes by default. Search your code for that value. Alternatively, it
may be overridden in the web.config file. As a quick test, you can set
session.timeout = 10 minutes. It should stick otherwise, you have something
funky going on in your app that you either don't know about or aren't
sharing.
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]
[Shameless Author plug]
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Professional VSTO.NET - Wrox/Wiley 2006
----
"Sai" <kumar877@.gmail.com> wrote in message
news:1145288352.456543.4650@.t31g2000cwb.googlegroups.com...
> Hi Alvin,
> thanks for the advise. Iam inputting the values to a text file when
> session times out. It is coming as 60 seconds. So the session is
> timing out at every 60 seconds, but I could not find where to change
> these value. I checked the web.config and machine.config and
> application pools .
> Let me know specific place to change this value.
> thanks,
> K
>
Nothing in the code, nothing in the web.config. It has to be some
other place. I have seen all my code and no where I am setting these
values.
I tried changing session timeout to 10 minutes and still nothing
happens. So it got to be some where, not that simple.
Where else it can be.?
Thanks.
K
you need that check. go back and put it in there so that your application
can be resilient to memory issues. However, raise the limit to around 1gig
or so. The reason for this is that the application pool should be recycled
if an errant application (your code) decides to hog memory. Removing that
check prevents detection of this and other conditions.
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]
[Shameless Author plug]
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Professional VSTO.NET - Wrox/Wiley 2006
----
"Sai" <kumar877@.gmail.com> wrote in message
news:1145306983.181641.177810@.i40g2000cwc.googlegroups.com...
> Thanks for all your help. It got fixed just now. The problem is
> Virtual memory was so low (250MB), so every time a worker process
> initiates it goes to 250 MB and it recycles, so what we did was, we
> just removed the check box next to virtual memory of application pool.
> that's it. It works...great relief.
> Thanks,
> K
>
Thanks for all your help. It got fixed just now. The problem is
Virtual memory was so low (250MB), so every time a worker process
initiates it goes to 250 MB and it recycles, so what we did was, we
just removed the check box next to virtual memory of application pool.
that's it. It works...great relief.
Thanks,
K
Where is the Virtual memory checked/set? Somewhere in IIS?
Ron

Session Timeout.

Friends,

We have a simple application which has login page, users login to it
and enter their contact details and all other stuff. It is working
fine. Now we have moved to new windows 2003 server. The page works
but it gets refreshed every 5 mintues and goes back to login.aspx page.
How do I fix this.

Thanks for any help.

KAdd this in your Web.config file to elongate Session to 60min for example:

<sessionState cookieless="UseCookies" mode="InProc" timeout="60" /
but add it between
<system.web> </system.web>
--

Bishoy George
bishoy@.bishoy.com
20102550399

--------

"Sai" <kumar877@.gmail.com> wrote in message
news:1145074352.770881.44720@.u72g2000cwu.googlegro ups.com...
> Friends,
> We have a simple application which has login page, users login to it
> and enter their contact details and all other stuff. It is working
> fine. Now we have moved to new windows 2003 server. The page works
> but it gets refreshed every 5 mintues and goes back to login.aspx page.
> How do I fix this.
> Thanks for any help.
> K
no that did not help. same thing is happening again.
Do you have code in your page to redirect to your login page? Sounds like
your session is timing out and your code is kicking in to repost. Write some
code in your session_end event handler to dump a file with a time-stamp to
tell you when the session is dying. You can trouble-shoot from there.

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Professional VSTO.NET - Wrox/Wiley 2006
-----------------

"Sai" <kumar877@.gmail.com> wrote in message
news:1145116360.101576.258960@.i40g2000cwc.googlegr oups.com...
> no that did not help. same thing is happening again.
Hi Alvin,

thanks for the advise. Iam inputting the values to a text file when
session times out. It is coming as 60 seconds. So the session is
timing out at every 60 seconds, but I could not find where to change
these value. I checked the web.config and machine.config and
application pools .

Let me know specific place to change this value.

thanks,
K
So you have an override somewhere in your code because the timeout value is
20 minutes by default. Search your code for that value. Alternatively, it
may be overridden in the web.config file. As a quick test, you can set
session.timeout = 10 minutes. It should stick otherwise, you have something
funky going on in your app that you either don't know about or aren't
sharing.

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Professional VSTO.NET - Wrox/Wiley 2006
-----------------

"Sai" <kumar877@.gmail.com> wrote in message
news:1145288352.456543.4650@.t31g2000cwb.googlegrou ps.com...
> Hi Alvin,
> thanks for the advise. Iam inputting the values to a text file when
> session times out. It is coming as 60 seconds. So the session is
> timing out at every 60 seconds, but I could not find where to change
> these value. I checked the web.config and machine.config and
> application pools .
> Let me know specific place to change this value.
> thanks,
> K
Nothing in the code, nothing in the web.config. It has to be some
other place. I have seen all my code and no where I am setting these
values.
I tried changing session timeout to 10 minutes and still nothing
happens. So it got to be some where, not that simple.
Where else it can be.?

Thanks.
K
Thanks for all your help. It got fixed just now. The problem is
Virtual memory was so low (250MB), so every time a worker process
initiates it goes to 250 MB and it recycles, so what we did was, we
just removed the check box next to virtual memory of application pool.
that's it. It works...great relief.

Thanks,
K
you need that check. go back and put it in there so that your application
can be resilient to memory issues. However, raise the limit to around 1gig
or so. The reason for this is that the application pool should be recycled
if an errant application (your code) decides to hog memory. Removing that
check prevents detection of this and other conditions.

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Professional VSTO.NET - Wrox/Wiley 2006
-----------------

"Sai" <kumar877@.gmail.com> wrote in message
news:1145306983.181641.177810@.i40g2000cwc.googlegr oups.com...
> Thanks for all your help. It got fixed just now. The problem is
> Virtual memory was so low (250MB), so every time a worker process
> initiates it goes to 250 MB and it recycles, so what we did was, we
> just removed the check box next to virtual memory of application pool.
> that's it. It works...great relief.
> Thanks,
> K
Where is the Virtual memory checked/set? Somewhere in IIS?

Ron
it's under one of the application pool health monitoring tabs in IIS

--

________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Professional VSTO.NET - Wrox/Wiley 2006
-----------------

"RonL" <sal_paradise_93@.yahoo.com> wrote in message
news:1145322157.561147.218050@.j33g2000cwa.googlegr oups.com...
> Where is the Virtual memory checked/set? Somewhere in IIS?
> Ron
I couldn't find it. I see you're talking about Windows 2003 and I'm
looking at IIS 5 and XP Pro on my local machine.

Ron
IIS 5 doesn't have these characteristics. sorry.

--

________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Professional VSTO.NET - Wrox/Wiley 2006
-----------------

"RonL" <sal_paradise_93@.yahoo.com> wrote in message
news:1145411388.245339.46900@.i40g2000cwc.googlegro ups.com...
>I couldn't find it. I see you're talking about Windows 2003 and I'm
> looking at IIS 5 and XP Pro on my local machine.
> Ron

session timeout.... again

Hi Everyone -

This session timeout thing has popped up again.

Is there a way to globally redirect the user to a timeout
page when the session variables have timed out?

I really don't want to add a check on each and every page
in the page_load that will check the session.

please advise...

I've tried to check the session variable in the global.asax
file in the

Sub Application_BeginRequest(ByVal sender As Object, ByVal e As EventArgs)
' Fires at the beginning of each request
if session.Item("company_id") is nothing then
response.Redirect("logout.aspx")
End If
End Sub

but the session object is not allowed in this context

any ideas would be appreciated

thanks
tonyAn alternate method will be create a small function in one of the module and then just call the function at the top of each page.

Function Is_Session_Alive will return Flase is session has lost its values otherwise True

At the start of each page
If Is_Session_Alive(Session("Language"), Session("Service"), Session("Department")) = False Then
Response.Redirect("DefaultErrorPage.aspx")
End If

Thanks
Shafiq
make a class inheriting the page and code there.

subsiquently inherit new class on every page

hemant

Session Timeout..

Also I would like to inform the user just before X seconds of page expiry. I
do not want to use alert(). Is it possible to display the message on the
tool bar as once the count down for expire starts.
Thanks,
Benjamin
"Steve C. Orr [MVP, MCSD]" <Steve@dotnet.itags.org.Orr.net> wrote in message
news:#lv4LermEHA.324@dotnet.itags.org.TK2MSFTNGP11.phx.gbl...
> You could try using the javascript setTimeout function set to 20 minutes
> (the default session timeout period) and then set the
> document.location.href='login.aspx' via client side code.
> Here's an example of using the javascript setTimeout function:
> http://www.crowes.f9.co.uk/Javascript/timer.htm
> --
> I hope this helps,
> Steve C. Orr, MCSD, MVP
> http://Steve.Orr.net
>
> "Benjamin Smith" <BenSmithNg@dotnet.itags.org.hotmail.com> wrote in message
> news:%23%23YjkXrmEHA.3608@dotnet.itags.org.TK2MSFTNGP09.phx.gbl...
visible
the
>Yes you can display a message to the status bar of the browser.
Here's a nice example:
http://simplythebest.net/scripts/DH...//Steve.Orr.net
"Benjamin" <BenSmithNg@.hotmail.com> wrote in message
news:uGdHQhQnEHA.3520@.TK2MSFTNGP11.phx.gbl...
> Also I would like to inform the user just before X seconds of page expiry.
> I
> do not want to use alert(). Is it possible to display the message on the
> tool bar as once the count down for expire starts.
> Thanks,
> Benjamin
>
> "Steve C. Orr [MVP, MCSD]" <Steve@.Orr.net> wrote in message
> news:#lv4LermEHA.324@.TK2MSFTNGP11.phx.gbl...
> visible
> the
>

Session Timeout..

Thanks for your answers.
Now I understand I have to use setTimeout to achieve my goal.
The link http://www.crowes.f9.co.uk/Javascript/timer.htm is really helpful.
Which client side event I should use to keep track the user is still using
the website.
Thanks,
Benjamin
"Steve C. Orr [MVP, MCSD]" <Steve@dotnet.itags.org.Orr.net> wrote in message
news:#lv4LermEHA.324@dotnet.itags.org.TK2MSFTNGP11.phx.gbl...
> You could try using the javascript setTimeout function set to 20 minutes
> (the default session timeout period) and then set the
> document.location.href='login.aspx' via client side code.
> Here's an example of using the javascript setTimeout function:
> http://www.crowes.f9.co.uk/Javascript/timer.htm
> --
> I hope this helps,
> Steve C. Orr, MCSD, MVP
> http://Steve.Orr.net
>
> "Benjamin Smith" <BenSmithNg@dotnet.itags.org.hotmail.com> wrote in message
> news:%23%23YjkXrmEHA.3608@dotnet.itags.org.TK2MSFTNGP09.phx.gbl...
visible
the
>The browser will keep track of that for you.
All you need is one client side event to fire once the trigger time has
elapsed and you want to warn the user.
You can name the event anything you want.
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net
"Benjamin" <BenSmithNg@.hotmail.com> wrote in message
news:uan1PfQnEHA.392@.tk2msftngp13.phx.gbl...
> Thanks for your answers.
> Now I understand I have to use setTimeout to achieve my goal.
> The link http://www.crowes.f9.co.uk/Javascript/timer.htm is really
> helpful.
> Which client side event I should use to keep track the user is still using
> the website.
> Thanks,
> Benjamin
>
> "Steve C. Orr [MVP, MCSD]" <Steve@.Orr.net> wrote in message
> news:#lv4LermEHA.324@.TK2MSFTNGP11.phx.gbl...
> visible
> the
>
The event would be the TimeOut Interval triggering the function that
setTimeOut refers to.
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
I get paid good money to
solve puzzles for a living
"Steve C. Orr [MVP, MCSD]" <Steve@.Orr.net> wrote in message
news:#wwlJFRnEHA.3868@.TK2MSFTNGP11.phx.gbl...
> The browser will keep track of that for you.
> All you need is one client side event to fire once the trigger time has
> elapsed and you want to warn the user.
> You can name the event anything you want.
> --
> I hope this helps,
> Steve C. Orr, MCSD, MVP
> http://Steve.Orr.net
>
> "Benjamin" <BenSmithNg@.hotmail.com> wrote in message
> news:uan1PfQnEHA.392@.tk2msftngp13.phx.gbl...
using
minutes
page.
>

Session Timeout..

Hi i had the same problem.
Buti fixed..
If u need a more detailed script let me know!
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!Yes, I need to know.
Benjamin
"naijacoder naijacoder" <naijacoder@.toughguy.net> wrote in message
news:eu0aGPsmEHA.3988@.tk2msftngp13.phx.gbl...
> Hi i had the same problem.
> Buti fixed..
> If u need a more detailed script let me know!
>
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!
But what do you really want to do?
"Benjamin Smith" <BenSmithNg@.hotmail.com> wrote in message
news:eFTtrasmEHA.2908@.TK2MSFTNGP12.phx.gbl...
> Yes, I need to know.
> Benjamin
> "naijacoder naijacoder" <naijacoder@.toughguy.net> wrote in message
> news:eu0aGPsmEHA.3988@.tk2msftngp13.phx.gbl...
>
Steve gave you the answer. In more detail:
Session times out (by default) 20 minutes after the last Request was
received by the client browser instance holding that SessionID in a
temporary cookie. As no request is received on the server, no response can
be sent to the client. Therefore, the redirect MUST occur on the client.
That means JavaScript. And that means that your JavaScript function should
fire just as the Session times out (20 minutes). You would use the
JavaScript setTimeOut() function to accomplish this.
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
I get paid good money to
solve puzzles for a living
"Benjamin Smith" <BenSmithNg@.hotmail.com> wrote in message
news:eFTtrasmEHA.2908@.TK2MSFTNGP12.phx.gbl...
> Yes, I need to know.
> Benjamin
> "naijacoder naijacoder" <naijacoder@.toughguy.net> wrote in message
> news:eu0aGPsmEHA.3988@.tk2msftngp13.phx.gbl...
>

Session timeouts

how can i disable session timeouts without affecting any program codings?You do NOT want to disable Session timeouts. Sessions time out for a very
good reason: Every time a user logs onto your site, a Session is created. If
you disabled their timeout, you would in essence, create a memory leak that
would take very little time to crash your application. What you SHOULD do is
handle Session timeouts effectively.
HTH,
Kevin Spencer
Microsoft MVP
.Net Developer
The sun never sets on
the Kingdom of Heaven
"Fraijo" <Fraijo@.discussions.microsoft.com> wrote in message
news:FAE5CDD2-A0DF-451A-92E5-F7DCDA5F4953@.microsoft.com...
> how can i disable session timeouts without affecting any program codings?

Session timeouts

Hi
I've just been told that closing your browser closes your session on the
web-site you are viewing, is this true? If so, is this the browser that init
iates
the closure, or the server?
Thanks
Kev"Mantorok" <spamthis@.spam.com> wrote in message
news:cbc5da882bbc88c8422cf73e68ca@.news.rmplc.co.uk...

> I've just been told that closing your browser closes your session on the
> web-site you are viewing, is this true?
Totally untrue. If you want to make sure that a session is closed, you need
to provide a mechanism for a user to initiate it i.e. some sort of "Log out"
facility which tears down the session. The server is simply waiting to
respond to requests from clients - it cannot know when a browser has been
closed.
Do a Google search - this topic has been discussed ad nauseum...
http://www.thescripts.com/forum/thread321607.html
"Mark Rae" <mark@.markN-O-S-P-A-M.co.uk> wrote in message
news:OjkCr%23AdGHA.4276@.TK2MSFTNGP03.phx.gbl...
> "Mantorok" <spamthis@.spam.com> wrote in message
> news:cbc5da882bbc88c8422cf73e68ca@.news.rmplc.co.uk...
>
> Totally untrue. If you want to make sure that a session is closed, you
> need to provide a mechanism for a user to initiate it i.e. some sort of
> "Log out" facility which tears down the session. The server is simply
> waiting to respond to requests from clients - it cannot know when a
> browser has been closed.
Thank you for clarifying my thoughts, when I first heard it I immediately
said "How does the server know the client closed the browser?", silenced
followed.....
Cheers
Kev
"Mark Rae" <mark@.markN-O-S-P-A-M.co.uk> wrote in message
news:OjkCr%23AdGHA.4276@.TK2MSFTNGP03.phx.gbl...
> "Mantorok" <spamthis@.spam.com> wrote in message
> news:cbc5da882bbc88c8422cf73e68ca@.news.rmplc.co.uk...
>
> Totally untrue. If you want to make sure that a session is closed, you
> need to provide a mechanism for a user to initiate it i.e. some sort of
> "Log out" facility which tears down the session. The server is simply
> waiting to respond to requests from clients - it cannot know when a
> browser has been closed.
Come to think of it - when I log in to my (internal) web-site it stores my
login in a session variable, however when I close the browser and re-open my
login session has gone.
What's happening here?
Thanks
Kev
"Mantorok" <mantorok@.mantorok.com> wrote in message
news:e3sbfk$6br$1@.newsfeed.th.ifl.net...

> Come to think of it - when I log in to my (internal) web-site it stores my
> login in a session variable, however when I close the browser and re-open
> my login session has gone.
> What's happening here?
Opening the browser again causes a new session to be created.
"Mark Rae" <mark@.markN-O-S-P-A-M.co.uk> wrote in message
news:Oy$AtTBdGHA.4912@.TK2MSFTNGP05.phx.gbl...
> "Mantorok" <mantorok@.mantorok.com> wrote in message
> news:e3sbfk$6br$1@.newsfeed.th.ifl.net...
>
> Opening the browser again causes a new session to be created.
Aha, thanks.
Kev
"Mantorok" <mantorok@.mantorok.com> wrote in message
news:e3scup$71j$1@.newsfeed.th.ifl.net...

> Aha, thanks.
http://www.google.com/search?source...22+IsNewSession
Covering a few items in this thread:
Closing your browser does nothing on the server. The server still waits
until timeout to get rid of the session. And, opening a browser creates a
new session. This means you now have two sessions, but you are only
connected to the newest session.
The way this works is through a session cookie, or server cookie. Even users
with normal cookies off can get these. There are some older browsers that
see both types of cookies as the same. And, yes, an industrious user can
refuse server cookies, as well. But it is rare.
When you open the browser, it will not reuse a server cookie, even if the
session has not timed out. This is for security purposes. So, it creates a
new connection and gets a new server cookie (session). If you open and close
the browser 100 times, you have 100 sessions until they time out, but you
cannot get to any for which you have closed the browser.
Another interesting topic. If you open a new browser instance using Control
+ N, both connect to the same session. If you use the menu, you have two
different sessions. Cool, eh?
Remember, the web is stateless, so it has no clue what the user is doing.
Gregory A. Beamer
****************************************
*********
Think Outside the Box!
****************************************
*********
"Mantorok" <spamthis@.spam.com> wrote in message
news:cbc5da882bbc88c8422cf73e68ca@.news.rmplc.co.uk...
> Hi
> I've just been told that closing your browser closes your session on the
> web-site you are viewing, is this true? If so, is this the browser that
> initiates the closure, or the server?
> Thanks
> Kev
>
Cowboy,
Very good.
How? an industrious user can
refuse server cookies, as well. But it is rare.
more details please thanks for the education
SA
"Cowboy (Gregory A. Beamer)" <NoSpamMgbworld@.comcast.netNoSpamM> wrote in
message news:eeghAWCdGHA.5048@.TK2MSFTNGP04.phx.gbl...
> Covering a few items in this thread:
> Closing your browser does nothing on the server. The server still waits
> until timeout to get rid of the session. And, opening a browser creates a
> new session. This means you now have two sessions, but you are only
> connected to the newest session.
> The way this works is through a session cookie, or server cookie. Even
> users with normal cookies off can get these. There are some older browsers
> that see both types of cookies as the same. And, yes, an industrious user
> can refuse server cookies, as well. But it is rare.
> When you open the browser, it will not reuse a server cookie, even if the
> session has not timed out. This is for security purposes. So, it creates a
> new connection and gets a new server cookie (session). If you open and
> close the browser 100 times, you have 100 sessions until they time out,
> but you cannot get to any for which you have closed the browser.
> Another interesting topic. If you open a new browser instance using
> Control + N, both connect to the same session. If you use the menu, you
> have two different sessions. Cool, eh?
> Remember, the web is stateless, so it has no clue what the user is doing.
> --
> Gregory A. Beamer
> ****************************************
*********
> Think Outside the Box!
> ****************************************
*********
> "Mantorok" <spamthis@.spam.com> wrote in message
> news:cbc5da882bbc88c8422cf73e68ca@.news.rmplc.co.uk...
>

Session Timeouts

H, I have noticed that when the session has timed out, and you refresh the
pag etc, you very often end up with debug messages etc. Is there any clean
way to handle this so the users will not see the stack trace ?
I know there is the option to turn on the friendly messages, will this do
the trick >?
Cheers
Best Regards
The Inimitable Mr NewbieWhat's the debug message? Is it because the code is assuming Session is vali
d
even though it's not? I suspect that might be the problem...
In any event, if you don't want your users to see unhandled exception inform
ation,
consider setting up an error redirect page via the <customErrors> element
in web.config.
http://msdn.microsoft.com/library/d...rorsSection.asp
-Brock
DevelopMentor
http://staff.develop.com/ballen

> H, I have noticed that when the session has timed out, and you refresh
> the pag etc, you very often end up with debug messages etc. Is there
> any clean way to handle this so the users will not see the stack trace
> ?
> I know there is the option to turn on the friendly messages, will this
> do the trick >?
> Cheers
> The Inimitable Mr Newbie
>

Session Time-out?

Hi,
I know this is an old problem and I've googled for it, but I've not really gotten wiser ...
My problem is the following:
I want my users to log on and then edit or add data via web forms. Sofar, so good. But I want to prevent time-outs so they don't have to logon continuously nor do I want to risk them to lose their data if thesession has expired before they could save it.
What's the best way to do that?
I've set the time-out in my web.config to 60, but that doesn't really change a thing.
Thanks a lot.
you can increase the timeout period as much as you want, but you'll be in rist of overloading your server's memory with sessions

Session Timeout?

Hello,
is there any possibility to do something when the
session timeouts via code not via the global.asax?
ThanksWhat do you mean, the global.asax is code.
"Vishal" <anonymous@.discussions.microsoft.com> wrote in message
news:0bba01c4f996$cb277d70$a401280a@.phx.gbl...
> Hello,
> is there any possibility to do something when the
> session timeouts via code not via the global.asax?
> Thanks
No.
You can only execute code,
when Session_OnEnd fires, via global.asax
Juan T. Llibre
ASP.NET MVP
===========
"Vishal" <anonymous@.discussions.microsoft.com> wrote in message
news:0bba01c4f996$cb277d70$a401280a@.phx.gbl...
> Hello,
> is there any possibility to do something when the
> session timeouts via code not via the global.asax?
> Thanks
The Global.asax can only run, when I make the folder an
IIS application right? Is it possible to run the
Global.asax without making the folder an IIS application?
Thanks so far.

>--Original Message--
>No.
>You can only execute code,
>when Session_OnEnd fires, via global.asax
>
>Juan T. Llibre
>ASP.NET MVP
>===========
>"Vishal" <anonymous@.discussions.microsoft.com> wrote in
message
>news:0bba01c4f996$cb277d70$a401280a@.phx.gbl...
>
>.
>
Again, no.
Global.asax will not execute unless the folder
is at least a virtual directory, or an application.
Juan T. Llibre
ASP.NET MVP
===========
"Vishal" <anonymous@.discussions.microsoft.com> wrote in message
news:090601c4f9a5$b5b71090$a301280a@.phx.gbl...
> The Global.asax can only run, when I make the folder an
> IIS application right? Is it possible to run the
> Global.asax without making the folder an IIS application?
> Thanks so far.
>
> message

Session Timeout?

Hello,

is there any possibility to do something when the
session timeouts via code not via the global.asax?

ThanksWhat do you mean, the global.asax is code.

"Vishal" <anonymous@.discussions.microsoft.com> wrote in message
news:0bba01c4f996$cb277d70$a401280a@.phx.gbl...
> Hello,
> is there any possibility to do something when the
> session timeouts via code not via the global.asax?
> Thanks
No.

You can only execute code,
when Session_OnEnd fires, via global.asax

Juan T. Llibre
ASP.NET MVP
===========
"Vishal" <anonymous@.discussions.microsoft.com> wrote in message
news:0bba01c4f996$cb277d70$a401280a@.phx.gbl...
> Hello,
> is there any possibility to do something when the
> session timeouts via code not via the global.asax?
> Thanks
The Global.asax can only run, when I make the folder an
IIS application right? Is it possible to run the
Global.asax without making the folder an IIS application?

Thanks so far.

>--Original Message--
>No.
>You can only execute code,
>when Session_OnEnd fires, via global.asax
>
>Juan T. Llibre
>ASP.NET MVP
>===========
>"Vishal" <anonymous@.discussions.microsoft.com> wrote in
message
>news:0bba01c4f996$cb277d70$a401280a@.phx.gbl...
>> Hello,
>>
>> is there any possibility to do something when the
>> session timeouts via code not via the global.asax?
>>
>> Thanks
>
>.
Again, no.

Global.asax will not execute unless the folder
is at least a virtual directory, or an application.

Juan T. Llibre
ASP.NET MVP
===========
"Vishal" <anonymous@.discussions.microsoft.com> wrote in message
news:090601c4f9a5$b5b71090$a301280a@.phx.gbl...
> The Global.asax can only run, when I make the folder an
> IIS application right? Is it possible to run the
> Global.asax without making the folder an IIS application?
> Thanks so far.
>>--Original Message--
>>No.
>>
>>You can only execute code,
>>when Session_OnEnd fires, via global.asax
>>
>>
>>
>>Juan T. Llibre
>>ASP.NET MVP
>>===========
>>"Vishal" <anonymous@.discussions.microsoft.com> wrote in
> message
>>news:0bba01c4f996$cb277d70$a401280a@.phx.gbl...
>>> Hello,
>>>
>>> is there any possibility to do something when the
>>> session timeouts via code not via the global.asax?
>>>
>>> Thanks
>>
>>
>>.
>

Session Timeouts

Which Session Timeout property is used by default.
Is it the one in IIS (900 seconds)
Machine.config (20 mins)
or
Web.config (20 mins)
Could someone explain how this works.
Or is it IIS just because that ends first?
Thanksasp.net does not use the IIS session - these are for classic asp
true session timeout only occurs with the inproc session manager running in
your app domain. for its configuration it defaults to machine.config, but
web.config overrides it , like all settings (unless overriding
machine.config has been disabled).
-- bruce (sqlwork.com)
"BillGatesFan" <klj_mcsd@.hotmail.com> wrote in message
news:1103664141.963104.39250@.z14g2000cwz.googlegroups.com...
| Which Session Timeout property is used by default.
|
| Is it the one in IIS (900 seconds)
|
| Machine.config (20 mins)
|
| or
|
| Web.config (20 mins)
|
| Could someone explain how this works.
| Or is it IIS just because that ends first?
|
| Thanks
|
BillGatesFan..
I have also asked this question once..
But after my research..i think Web.Config..overrides all of them.
Patrick
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!

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

Which Session Timeout property is used by default.

Is it the one in IIS (900 seconds)

Machine.config (20 mins)

or

Web.config (20 mins)

Could someone explain how this works.
Or is it IIS just because that ends first?

Thanksasp.net does not use the IIS session - these are for classic asp

true session timeout only occurs with the inproc session manager running in
your app domain. for its configuration it defaults to machine.config, but
web.config overrides it , like all settings (unless overriding
machine.config has been disabled).

-- bruce (sqlwork.com)

"BillGatesFan" <klj_mcsd@.hotmail.com> wrote in message
news:1103664141.963104.39250@.z14g2000cwz.googlegro ups.com...
| Which Session Timeout property is used by default.
|
| Is it the one in IIS (900 seconds)
|
| Machine.config (20 mins)
|
| or
|
| Web.config (20 mins)
|
| Could someone explain how this works.
| Or is it IIS just because that ends first?
|
| Thanks
|
BillGatesFan..
I have also asked this question once..
But after my research..i think Web.Config..overrides all of them.
Patrick

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Session Timeouts

H, I have noticed that when the session has timed out, and you refresh the
pag etc, you very often end up with debug messages etc. Is there any clean
way to handle this so the users will not see the stack trace ?

I know there is the option to turn on the friendly messages, will this do
the trick >?

Cheers

--
Best Regards

The Inimitable Mr NewbieWhat's the debug message? Is it because the code is assuming Session is valid
even though it's not? I suspect that might be the problem...

In any event, if you don't want your users to see unhandled exception information,
consider setting up an error redirect page via the <customErrors> element
in web.config.

http://msdn.microsoft.com/library/d...rorsSection.asp

-Brock
DevelopMentor
http://staff.develop.com/ballen

> H, I have noticed that when the session has timed out, and you refresh
> the pag etc, you very often end up with debug messages etc. Is there
> any clean way to handle this so the users will not see the stack trace
> ?
> I know there is the option to turn on the friendly messages, will this
> do the trick >?
> Cheers
> The Inimitable Mr Newbie

Session timeouts

Hi

I've just been told that closing your browser closes your session on the
web-site you are viewing, is this true? If so, is this the browser that initiates
the closure, or the server?

Thanks
Kev"Mantorok" <spamthis@.spam.com> wrote in message
news:cbc5da882bbc88c8422cf73e68ca@.news.rmplc.co.uk ...

> I've just been told that closing your browser closes your session on the
> web-site you are viewing, is this true?

Totally untrue. If you want to make sure that a session is closed, you need
to provide a mechanism for a user to initiate it i.e. some sort of "Log out"
facility which tears down the session. The server is simply waiting to
respond to requests from clients - it cannot know when a browser has been
closed.

Do a Google search - this topic has been discussed ad nauseum...
http://www.msdner.com/forum/thread321607.html
"Mark Rae" <mark@.markN-O-S-P-A-M.co.uk> wrote in message
news:OjkCr%23AdGHA.4276@.TK2MSFTNGP03.phx.gbl...
> "Mantorok" <spamthis@.spam.com> wrote in message
> news:cbc5da882bbc88c8422cf73e68ca@.news.rmplc.co.uk ...
>> I've just been told that closing your browser closes your session on the
>> web-site you are viewing, is this true?
> Totally untrue. If you want to make sure that a session is closed, you
> need to provide a mechanism for a user to initiate it i.e. some sort of
> "Log out" facility which tears down the session. The server is simply
> waiting to respond to requests from clients - it cannot know when a
> browser has been closed.

Thank you for clarifying my thoughts, when I first heard it I immediately
said "How does the server know the client closed the browser?", silenced
followed.....

Cheers
Kev
"Mark Rae" <mark@.markN-O-S-P-A-M.co.uk> wrote in message
news:OjkCr%23AdGHA.4276@.TK2MSFTNGP03.phx.gbl...
> "Mantorok" <spamthis@.spam.com> wrote in message
> news:cbc5da882bbc88c8422cf73e68ca@.news.rmplc.co.uk ...
>> I've just been told that closing your browser closes your session on the
>> web-site you are viewing, is this true?
> Totally untrue. If you want to make sure that a session is closed, you
> need to provide a mechanism for a user to initiate it i.e. some sort of
> "Log out" facility which tears down the session. The server is simply
> waiting to respond to requests from clients - it cannot know when a
> browser has been closed.

Come to think of it - when I log in to my (internal) web-site it stores my
login in a session variable, however when I close the browser and re-open my
login session has gone.

What's happening here?

Thanks
Kev
"Mantorok" <mantorok@.mantorok.com> wrote in message
news:e3sbfk$6br$1@.newsfeed.th.ifl.net...

> Come to think of it - when I log in to my (internal) web-site it stores my
> login in a session variable, however when I close the browser and re-open
> my login session has gone.
> What's happening here?

Opening the browser again causes a new session to be created.
"Mark Rae" <mark@.markN-O-S-P-A-M.co.uk> wrote in message
news:Oy$AtTBdGHA.4912@.TK2MSFTNGP05.phx.gbl...
> "Mantorok" <mantorok@.mantorok.com> wrote in message
> news:e3sbfk$6br$1@.newsfeed.th.ifl.net...
>> Come to think of it - when I log in to my (internal) web-site it stores
>> my login in a session variable, however when I close the browser and
>> re-open my login session has gone.
>>
>> What's happening here?
> Opening the browser again causes a new session to be created.

Aha, thanks.

Kev
"Mantorok" <mantorok@.mantorok.com> wrote in message
news:e3scup$71j$1@.newsfeed.th.ifl.net...

> Aha, thanks.

http://www.google.com/search?source...22+IsNewSession
Covering a few items in this thread:

Closing your browser does nothing on the server. The server still waits
until timeout to get rid of the session. And, opening a browser creates a
new session. This means you now have two sessions, but you are only
connected to the newest session.

The way this works is through a session cookie, or server cookie. Even users
with normal cookies off can get these. There are some older browsers that
see both types of cookies as the same. And, yes, an industrious user can
refuse server cookies, as well. But it is rare.

When you open the browser, it will not reuse a server cookie, even if the
session has not timed out. This is for security purposes. So, it creates a
new connection and gets a new server cookie (session). If you open and close
the browser 100 times, you have 100 sessions until they time out, but you
cannot get to any for which you have closed the browser.

Another interesting topic. If you open a new browser instance using Control
+ N, both connect to the same session. If you use the menu, you have two
different sessions. Cool, eh?

Remember, the web is stateless, so it has no clue what the user is doing.

--
Gregory A. Beamer

*************************************************
Think Outside the Box!
*************************************************
"Mantorok" <spamthis@.spam.com> wrote in message
news:cbc5da882bbc88c8422cf73e68ca@.news.rmplc.co.uk ...
> Hi
> I've just been told that closing your browser closes your session on the
> web-site you are viewing, is this true? If so, is this the browser that
> initiates the closure, or the server?
> Thanks
> Kev
Cowboy,

Very good.

How? an industrious user can
refuse server cookies, as well. But it is rare.

more details please thanks for the education

SA

"Cowboy (Gregory A. Beamer)" <NoSpamMgbworld@.comcast.netNoSpamM> wrote in
message news:eeghAWCdGHA.5048@.TK2MSFTNGP04.phx.gbl...
> Covering a few items in this thread:
> Closing your browser does nothing on the server. The server still waits
> until timeout to get rid of the session. And, opening a browser creates a
> new session. This means you now have two sessions, but you are only
> connected to the newest session.
> The way this works is through a session cookie, or server cookie. Even
> users with normal cookies off can get these. There are some older browsers
> that see both types of cookies as the same. And, yes, an industrious user
> can refuse server cookies, as well. But it is rare.
> When you open the browser, it will not reuse a server cookie, even if the
> session has not timed out. This is for security purposes. So, it creates a
> new connection and gets a new server cookie (session). If you open and
> close the browser 100 times, you have 100 sessions until they time out,
> but you cannot get to any for which you have closed the browser.
> Another interesting topic. If you open a new browser instance using
> Control + N, both connect to the same session. If you use the menu, you
> have two different sessions. Cool, eh?
> Remember, the web is stateless, so it has no clue what the user is doing.
> --
> Gregory A. Beamer
> *************************************************
> Think Outside the Box!
> *************************************************
> "Mantorok" <spamthis@.spam.com> wrote in message
> news:cbc5da882bbc88c8422cf73e68ca@.news.rmplc.co.uk ...
>> Hi
>>
>> I've just been told that closing your browser closes your session on the
>> web-site you are viewing, is this true? If so, is this the browser that
>> initiates the closure, or the server?
>>
>> Thanks
>> Kev
>>
>>

Session timeouts

how can i disable session timeouts without affecting any program codings?You do NOT want to disable Session timeouts. Sessions time out for a very
good reason: Every time a user logs onto your site, a Session is created. If
you disabled their timeout, you would in essence, create a memory leak that
would take very little time to crash your application. What you SHOULD do is
handle Session timeouts effectively.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
The sun never sets on
the Kingdom of Heaven

"Fraijo" <Fraijo@.discussions.microsoft.com> wrote in message
news:FAE5CDD2-A0DF-451A-92E5-F7DCDA5F4953@.microsoft.com...
> how can i disable session timeouts without affecting any program codings?
You do NOT want to disable Session timeouts. Sessions time out for a very
good reason: Every time a user logs onto your site, a Session is created. If
you disabled their timeout, you would in essence, create a memory leak that
would take very little time to crash your application. What you SHOULD do is
handle Session timeouts effectively.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
The sun never sets on
the Kingdom of Heaven

"Fraijo" <Fraijo@.discussions.microsoft.com> wrote in message
news:FAE5CDD2-A0DF-451A-92E5-F7DCDA5F4953@.microsoft.com...
> how can i disable session timeouts without affecting any program codings?

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 times out too soon...

Friends,

My web.config session setting is timeout=20, but in code we set the timeout
to override this to some user preference, often 40 minutes, (specified by
the user in seconds). But even in fairly active sessions, (ones where post
are done every 5 minutes or less), we still have session timing out.
Whether either the 20 minute or 40 minute value is in effect, I never wait
more than 5 minutes between posts back to the server (doing real work) so I
would NOT expect a session timeout.

Does anybody have any ideas about how to track this down? Are others having
similar results? Do I need to provide more data to make sense?

Thanks in advance for your time. I've been in software for 20+ years, but
new to ASP.NET. Our actual ASP.NET developers are baffled too.

Thanks! Sincerely,

James Hunter Ross
Senior Software Developer
O'Neil Software, Inc.
james.ross@dotnet.itags.org.oneilsoft.comJames Hunter Ross wrote:
> Friends,
> My web.config session setting is timeout=20, but in code we set the
> timeout to override this to some user preference, often 40 minutes,
> (specified by the user in seconds). But even in fairly active
> sessions, (ones where post are done every 5 minutes or less), we
> still have session timing out. Whether either the 20 minute or 40
> minute value is in effect, I never wait more than 5 minutes between
> posts back to the server (doing real work) so I would NOT expect a
> session timeout.

If you really are seeing Session loss (instead of something else that only
looks like Session loss), the most common cause would be an app domain
restart, assuming you are using InProc Session state.

Check the ASP.NET v1.1.4322 object in perfmon. There is a counter for
Application Restarts. Monitor that when you lose Session. If it increments
at the same time, your app domain recycling is causing the problem.

The most common cause of app domain restarts is file change notifications.
That would be caused by anti-virus or something else scanning the
application or from someone changing the web.config in the root folder or
something in the bin.

--
Jim Cheshire
JIMCO Software
http://www.jimcosoftware.com

FrontPage add-ins for FrontPage 2000 - 2003

I also experienced this issue and found Jim's post regarding
sessionState mode to be helpful.

I changed my sessionState mode from the default inproc to StateServer.
Of course, this is one of those situations where, after the change, I'm
waiting for the application to, uh, NOT break. But so far so good.

One question I had for Jim is about perfmon. This looks like a really
neat tool - I just wish I knew how to use it.

When you say to 'Check the ASP.NET v1.1.4322 object in perfmon' - how
does one do that?

Cheers,
Robert Meyer
ISG
http://www.isgcom.com

*** Sent via Developersdex http://www.developersdex.com ***
Robert Meyer wrote:
> When you say to 'Check the ASP.NET v1.1.4322 object in perfmon' - how
> does one do that?

Hi Robert,

Perfmon (Performance) is in Administrative Tools. When you launch it,
choose "ASP.NET v1.1.4322" from the object dropdown. That will populate the
Counter and Instance listboxes. Choose "Application Restarts" from the
Counter listbox and then choose your process (or Global) from the instance
listbox. Then click Add and then Close.

Now you will have an item in the listbox at the bottom of Perfmon for
Application Restarts. If you select it, you'll see a graph representation
and numeric values for that counter. If you see that increment when your
problem occurs, you'll know it was because of an app domain restart.

--
Jim Cheshire
JIMCO Software
http://www.jimcosoftware.com

Session timeouts and dynamic MasterPages

Hi,

I have a site which uses dynamic MasterPages. The selection of the
MasterPage to use is determined by an encrypted QueryString. Session_Start
looks for the presence of the QueryString, decrypts it, and sets up a
Session variable holding the name of the MasterPage to use. The contents
pages interrogate this Session variable in the Page_PreInit method (has to
be done here) and apply the correct MasterPage accordingly.

Works perfectly, until / unless the session times out. I'm checking for this
at the top of the Page_PreInit method using if (Session.IsNewSession) - this
works. If the IsNewSession is true, then the code redirects to a generic
page informing the user that they have been idle too long, and that they
must log in again. Fairly standard stuff.

HOWEVER, the problem I have is that the contents page then continues to load
i.e. its Page_Load fires, even though I've redirected to a different page.
I've worked round this by use of a boolean variable, as follows:

The code is as below:

bool blnTimedOut = false; // fudge variable

private void Page_PreInit(object sender, System.EventArgs e)
{
if (Session.IsNewSession)
{
blnTimedOut = true; // fudge code
Response.Redirect("~/sessionTimedOut.htm", false);
return;
}
this.MasterPageFile = "~/master/" + Session["strSite"].ToString() +
".master";
}

protected void Page_Load(object sender, EventArgs e)
{
// this event fires even though Response.Redirect in Page_PreInit
if (blnTimedOut ) // fudge code
{
return;
}
// rest of Page_Load code
}

Whilst the above most certainly works, I'm wondering if there is a better /
neater / more efficient way of doing this. E.g. is there a property of the
Page object that I can set in Page_PreInit to tell it not to fire any
further Page events...? I've done a trawl through MSDN and Google but have
drawn a blank...

Any assistance gratefully received.

MarkMark,
Don't think so. I say, If it ain't broke, don't fix it!
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
"Mark Rae" wrote:

Quote:

Originally Posted by

Hi,
>
I have a site which uses dynamic MasterPages. The selection of the
MasterPage to use is determined by an encrypted QueryString. Session_Start
looks for the presence of the QueryString, decrypts it, and sets up a
Session variable holding the name of the MasterPage to use. The contents
pages interrogate this Session variable in the Page_PreInit method (has to
be done here) and apply the correct MasterPage accordingly.
>
Works perfectly, until / unless the session times out. I'm checking for this
at the top of the Page_PreInit method using if (Session.IsNewSession) - this
works. If the IsNewSession is true, then the code redirects to a generic
page informing the user that they have been idle too long, and that they
must log in again. Fairly standard stuff.
>
HOWEVER, the problem I have is that the contents page then continues to load
i.e. its Page_Load fires, even though I've redirected to a different page.
I've worked round this by use of a boolean variable, as follows:
>
The code is as below:
>
bool blnTimedOut = false; // fudge variable
>
private void Page_PreInit(object sender, System.EventArgs e)
{
if (Session.IsNewSession)
{
blnTimedOut = true; // fudge code
Response.Redirect("~/sessionTimedOut.htm", false);
return;
}
this.MasterPageFile = "~/master/" + Session["strSite"].ToString() +
".master";
}
>
protected void Page_Load(object sender, EventArgs e)
{
// this event fires even though Response.Redirect in Page_PreInit
if (blnTimedOut ) // fudge code
{
return;
}
// rest of Page_Load code
}
>
>
Whilst the above most certainly works, I'm wondering if there is a better /
neater / more efficient way of doing this. E.g. is there a property of the
Page object that I can set in Page_PreInit to tell it not to fire any
further Page events...? I've done a trawl through MSDN and Google but have
drawn a blank...
>
Any assistance gratefully received.
>
Mark
>
>
>

"Peter Bromberg [C# MVP]" <pbromberg@.yahoo.nospammin.comwrote in message
news:6B9E1F51-8A8C-4545-9C52-B4868DEA43F1@.microsoft.com...

Quote:

Originally Posted by

Don't think so.

OK.

Quote:

Originally Posted by

I say, If it ain't broke, don't fix it!

Well, yeah, but I'm always interested in finding better ways of doing
things...

Maybe there are none in this particular case... There certainly seems to be
no way of one of the "early" Page methods telling the "later" ones not to
fire... This can get annoying if the creation of the page needs to be
aborted in the Page_PreInit, and you subsquently have Page_Init, Page_Load,
Page_PreRender and Page_Unload... :-)

Nil desperandum - it works...
Hmmm.
I suppose you *could* do that, e.g. have a boolean somewhere and the "early"
lifecycle method / event can set this, and your code in the later one would
check for it and only execute certain code if it's true, no?
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
"Mark Rae" wrote:

Quote:

Originally Posted by

"Peter Bromberg [C# MVP]" <pbromberg@.yahoo.nospammin.comwrote in message
news:6B9E1F51-8A8C-4545-9C52-B4868DEA43F1@.microsoft.com...
>

Quote:

Originally Posted by

Don't think so.

>
OK.
>

Quote:

Originally Posted by

I say, If it ain't broke, don't fix it!

>
Well, yeah, but I'm always interested in finding better ways of doing
things...
>
Maybe there are none in this particular case... There certainly seems to be
no way of one of the "early" Page methods telling the "later" ones not to
fire... This can get annoying if the creation of the page needs to be
aborted in the Page_PreInit, and you subsquently have Page_Init, Page_Load,
Page_PreRender and Page_Unload... :-)
>
Nil desperandum - it works...
>
>
>

"Peter Bromberg [C# MVP]" <pbromberg@.yahoo.nospammin.comwrote in message
news:C53DF6B7-E05D-4B2A-B949-FC9E6CB1494E@.microsoft.com...

Quote:

Originally Posted by

I suppose you *could* do that, e.g. have a boolean somewhere and the
"early"
lifecycle method / event can set this, and your code in the later one
would
check for it and only execute certain code if it's true, no?

Er, did you actually *read* the code in my original post...?

That is *precisely* what I'm doing... ;-)