Thanks Ian, I figured it out now. I was trying to update the database based on the session id and token. But since the session had timed out, those values didn't exist.
As I figured out, you have to use the "sessionScope" argument in onSessionEnd to get at those values. Once I did that everything works as it should. I wasn't seeing the session time out originally, because I had my sessionTracker within the same application, so hitting the sessionTracker was renewing the session - thus it never timed out. Duh. -- Josh ----- Original Message ----- From: "Ian Skinner" <[EMAIL PROTECTED]> To: "CF-Talk" <[email protected]> Sent: Tuesday, February 20, 2007 2:48 PM Subject: RE: App.cfc onSessionEnd not firing when session times out? > So, if the session doesn't effectively end when it times out, can I use > onSessionEnd to do what I want to do, or is there another way? Or am I > missing something obvious? > > -- Josh > > What are you doing when the session ends? I've not done much with these > events, but when I played with it, I recall it working fairly well for me. > > The one caveat I learned was the deference of a user being dissociated > with a session and the session ending. If you have set up sessions to > "memory" cookies so that the cfide/cftoken values are lost when a browser > is closed, this does not create a session end event. The event does not > fire until the time out period has occurred. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 and Flex 2 Build sales & marketing dashboard RIAâs for your business. Upgrade now http://www.adobe.com/products/coldfusion/flex2 Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:270256 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
