Session_OnEnd not firing sometimes?

[Chris Ashley]

There seem to be isolated occurences of Session_OnEnd not firing in my
app. This is problematic because some clean up of resources happens
here. I know the Session events were unreliable in classic ASP, but is
this still the case in ASP.Net?

What kind of scenarios would case Session_OnEnd not to fire? Would
Application_Error being hit cause Session_OnEnd not to fire?

[Michael Nemtsev [MVP]]

Hello Chris,

yep, it's still not relyable.
1) it works only for the InProc session management
2) With some SP (for VS or for Windows) it doesn't work at all - need hotfix


---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo
CAThere seem to be isolated occurences of Session_OnEnd not firing in
CAmy app. This is problematic because some clean up of resources
CAhappens here. I know the Session events were unreliable in classic
CAASP, but is this still the case in ASP.Net?
CA>
CAWhat kind of scenarios would case Session_OnEnd not to fire? Would
CAApplication_Error being hit cause Session_OnEnd not to fire?
CA>

[Chris Ashley]

Hi michael,

Thanks for your response.

Is there any alternative? Maybe I could store some object in the
session and have its finalizer do the clear up? Would this work, so
when it is garbage collected (presumably at some point after there is
no reference to it in Session scope), my clean up will happen because
GC will call it's finalizer?

On 12 Dec, 12:43, Michael Nemtsev [MVP] <[e-mail]:

Hello Chris,

yep, it's still not relyable.
1) it works only for the InProc session management
2) With some SP (for VS or for Windows) it doesn't work at all - need hotfix

---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog:http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

CAThere seem to be isolated occurences of Session_OnEnd not firing in
CAmy app. This is problematic because some clean up of resources
CAhappens here. I know the Session events were unreliable in classic
CAASP, but is this still the case in ASP.Net?
CA>
CAWhat kind of scenarios would case Session_OnEnd not to fire? Would
CAApplication_Error being hit cause Session_OnEnd not to fire?
CA>

[Michael Nemtsev [MVP]]

Hello Chris,

You can use Application and Cache instead

read the MSDN to get more info about this
---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo
CAHi michael,
CA>
CAThanks for your response.
CA>
CAIs there any alternative? Maybe I could store some object in the
CAsession and have its finalizer do the clear up? Would this work, so
CAwhen it is garbage collected (presumably at some point after there
CAis no reference to it in Session scope), my clean up will happen
CAbecause GC will call it's finalizer?
CA>
CAOn 12 Dec, 12:43, Michael Nemtsev [MVP] <[e-mail]:
CA>

>Hello Chris,

yep, it's still not relyable.
1) it works only for the InProc session management
2) With some SP (for VS or for Windows) it doesn't work at all - need
hotfix
---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog:http://spaces.live.com/laflour
"The greatest danger for most of us is not that our aim is too high
and we miss it, but that it is too low and we reach it" (c)
Michelangelo

CAThere seem to be isolated occurences of Session_OnEnd not firing
in
CAmy app. This is problematic because some clean up of resources
CAhappens here. I know the Session events were unreliable in
classic
CAASP, but is this still the case in ASP.Net?
CA>
CAWhat kind of scenarios would case Session_OnEnd not to fire?
Would
CAApplication_Error being hit cause Session_OnEnd not to fire?
CA>

[Hal Rosser]

"Chris Ashley" <ch***********@gmail.comwrote in message
news:4e**********************************@e67g2000 hsc.googlegroups.com...

There seem to be isolated occurences of Session_OnEnd not firing in my
app. This is problematic because some clean up of resources happens
here. I know the Session events were unreliable in classic ASP, but is
this still the case in ASP.Net?

What kind of scenarios would case Session_OnEnd not to fire? Would
Application_Error being hit cause Session_OnEnd not to fire?

I think the Session timeout can be set on the server,