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=34107>. 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=34107 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2006-02-02 17:54 ------- I'm sorry but I also think this is a bug of tomcat 5. See this mail (called session.invalidate() change) : http://www.mail-archive.com/users@tomcat.apache.org/msg01377.html I have the exact same trouble, and while testing tomcat 5.5.15 with our apps, I confirm this is the only webapp server I know that doesn't at least allow the servlet to get the ID of the session that was invalidated (and why not all the other stuff... after all it's up to the developper to know what he's doing...). We need this id for cache cleaning here, so far I can't validate tomcat 5.x with our webapps because we'll have memory leak, unless users properly exit the application everytime, which they do of course not :) Any reason for this change ? -- 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]
