Andrew.. you might be right - bringing me back to my original point; 1. remove OnError. 2. try/catch/dump/email in the OnSessionEnd method for debugging purposes and to hopefully end the 'over complication'.
Peter, sessions end (j2ee or not) when they 'expire' too. This is when the on OnSessionEnd and maybe OnError event is fired, no? On 5/14/07, Peter Tilbrook <[EMAIL PROTECTED]> wrote: > > > Why do you fellas over complicate things? > > I mean thing about it? OnRequestEnd? OnSessionEnd? > > The only to really end a session with CF is to use J2EE sessions. > Browser is closed - session is ended. Of course depending on how you > code your app this may not bet the case. > > My host no longer allows "J2EE" sessions so true session management is > screwed by bad server management. Out of my control. It shits me but > badder things have happened. > > So why no J2EE support? Apparently my "good" code has to be back > pedalled so the "bad" code that does not handle sessions correctly. > And the bad code is the crash server type code so go figure. > > NB this is only CF with J2EE (MX 6.x+). > > > > > > > -- > Peter Tilbrook > ColdGen Internet Solutions > President, ACT and Region ColdFusion Users Group > PO Box 2247 > Queanbeyan, NSW, 2620 > AUSTRALIA > > http://www.coldgen.com/ > http://www.actcfug.com/ > > Tel: +61-2-6284-2727 > Mob: +61-0432-897-437 > > Email: [EMAIL PROTECTED] > MSN Messenger Live: Desktop General > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
