DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33711>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711 ------- Additional Comments From [EMAIL PROTECTED] 2005-02-24 17:11 ------- (In reply to comment #1 from Remy) > You might want to look into the code a little bit more, and see that SSO should > get an event for all sessions of a particular webapp when it is stopped. Remy, OK I'm confused... I've only just started to look at the internals of Tomcat, so its kind of hard to initially get my head around the codebase. However, I've been instrumenting a local copy of the 5.5.7 source with lots of extra logging to try to follow the logic. >From what I can tell, the SingleSignOn is NOT notified in any way when an application is undeployed. The only mechanism I could see would be if it was told when the individual sessions were expired. So I had a look at session.StandardManager, which seems to deal with persisting and expiring all of the sessions when an application is STOPped. However, looking at StandardManager.doUnload(), the look that expires the sessions calls session.expire(false) - i.e. does not notify listeners, hence the SSO never gets told. Did I miss something obvious? (I am trying to look into the problem and help out here!) In the meantime, a colleague is still fighting with the loggers and class loaders, but I think we can accept that is a separate issue. Thanks, Kev -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
