SESSION_END Questions

[Ron Vecchi]

1.) If I want to use an object that was stored in the Application state will
it be avilable in the Session_End event. (even on the last session to end)??
2.) Can I use the current sessions state in its own session_end event??

I asked because I am trying to log some data in this event and use both
scenarios above but nothing is happening.


Thanks!
Ron

 

[Guest]

What happens if you set your session expration to say 1 minute, put a
breakpoint in those events you are interested in, and check the app and
session state yourself?

 

[Joel Zinn]

From what I have seen, you can set the exp at 1 min and put a break point in
the code and have the break point work in debug mode. However, that does
not necessarily mean that it will work during normal running.

I have worked with this very scenario. What I found was that if you made
external calls to any data classes you built in the Session_End event, the
code does not seem to be executing. When I removed the external calls with
complete code in the End method, it works. It is a real pain in the
you-know-where, but it does work, at least for me. But, it is very flakey.

----Joel Zinn

 

[Ron]

What I was trying to do was log all web traffic made by the current session
and only store it in the database when the session ends. Seems like this
can't be done then...

Has anyone tried this? or no a way around it?

 

[Joel Zinn]

Yes, that is what I am doing. I guess I wasn't clear with what we have
done. The only way we could consistently get our db log entries created was
to code the entire database Insert code in the Session_End. That way we did
not have to call out to one of our dataclasses, which is apparently where
the problem with Global.Session_End lie. If you call an outside object, it
it very internmittent.

 

[Ron]

well thats unfortunate,

Thanks!

Yes, that is what I am doing. I guess I wasn't clear with what we have
done. The only way we could consistently get our db log entries created
was to code the entire database Insert code in the Session_End. That way
we did not have to call out to one of our dataclasses, which is apparently
where the problem with Global.Session_End lie. If you call an outside
object, it it very internmittent.