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=40593>. 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=40593 Summary: HttpSessionListener#sessionDestroyed is not called though the manager's pathname is emply. Product: Tomcat 5 Version: 5.5.17 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] I defined pathname="" in the Manager tag, because I did not want to continue sessions even if my application(or tomcat) is reactivated. As a result, sessions are not stored in the file "SESSIONS.ser", but HttpSessionListener#sessionDestroyed is not called. I think following logic is the cause: --- ...In StandardContext#stop() // Stop our filters filterStop(); // Stop our application listeners listenerStop(); // Stop ContainerBackgroundProcessor thread super.threadStop(); if ((manager != null) && (manager instanceof Lifecycle)) { ((Lifecycle) manager).stop(); } --- I think it would be better that listenerStop() is called after manager#stop(), or that we do not set null to applicationLifecycleListenersObjects in listenerStop() method at least for the HttpSessionListener instance. -- 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]
