DO NOT REPLY [Bug 36994] - httpsession.getId() throws ISE after invalidation
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=36994. 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=36994 --- Additional Comments From [EMAIL PROTECTED] 2005-10-12 14:34 --- Hi William, the servlet spec 2.4 doesn't throw the ISE. The new servlet spec 2.5 throws the ISE. So that's a change between 2.4 and 2.5. Strange on this is, that this change isn't listed in der change list between 2.4 and 2.5. I know that in the future the ISE will come, but the TC homepage says that the current TC 5.5 is an impl for the final 2.4 spec - not for the non-final 2.5 spec. -- 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]
DO NOT REPLY [Bug 36994] - httpsession.getId() throws ISE after invalidation
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=36994. 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=36994 --- Additional Comments From [EMAIL PROTECTED] 2005-10-12 14:41 --- (In reply to comment #3) Hi William, the servlet spec 2.4 doesn't throw the ISE. The new servlet spec 2.5 throws the ISE. So that's a change between 2.4 and 2.5. Strange on this is, that this change isn't listed in der change list between 2.4 and 2.5. I know that in the future the ISE will come, but the TC homepage says that the current TC 5.5 is an impl for the final 2.4 spec - not for the non-final 2.5 spec. No the spec didn't change. However, it turned out that getId should have thrown an ISE, while in Tomcat it did not. If you want to work around it, you can modify the Tomcat code easily. http://jcp.org/aboutJava/communityprocess/maintenance/jsr154/errata204.txt -- 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]
DO NOT REPLY [Bug 36994] - httpsession.getId() throws ISE after invalidation
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=36994. 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=36994 --- Additional Comments From [EMAIL PROTECTED] 2005-10-11 17:15 --- I agree with Lars. I use a Map (stored as an attribute of the ServletContext) to keep track of the active http sessions. Using Tomcat 5.5.9 I didn't have any problem logging-out, but with Tomcat 5.5.12 when I try to invalidate a session I get an ISE (getId: Session already invalidated). (In reply to comment #0) After a http session is invalidated a call to getId() throws an IllegalStateException(already invalidated). I think this doesn't conform to the servlet spec that doesn't say anything about an ISE in the api doc. All ISEs that can be thrown by the session-methods are explicit listed. Beside this it is very essential to have the sessionId at least during HttpSessionBindingListener.valueUnbound() if this method is called during the invalidation. The api doc of valueUnbound() says: Notifies the object that it is being unbound from a session and identifies the session. The session is identified by its Id, but if the Id is not accessible anymore... The ISE was inserted in Version 5.5.10: excerpt from the changelog: Re-add patch causing Session.getId to throw an ISE, and make all internal components use a safe getIdInternal Thanks Lars -- 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]
DO NOT REPLY [Bug 36994] - httpsession.getId() throws ISE after invalidation
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=36994. 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=36994 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2005-10-11 19:19 --- This is now required by the servlet spec, so it can't be changed by Tomcat. See: http://jcp.org/aboutJava/communityprocess/maintenance/jsr154/154errata.txt If the Servlet Expert Group decides to change this at some future point, then Tomcat can consider removing the ISE. Until then, the only place to complain about this is: [EMAIL PROTECTED] -- 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]
