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=29283>. 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=29283 Exception: StandardSession.invalidate [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2004-05-28 19:37 ------- What exactly does this mean? The servlet spec specifies that if an BindingListener is unbound from a session because the session expired, then the event occurs after the session is invalidated. I am running a vendor supplied application and the session associated with this error is not receiving the session timeout and therefore is retaining the session as active. It would appear that the exception interrupted the process whereby the application is notified of the session termination. If this is not a problem, then why is the exception thrown? Why isn't the application notified of the session termination? If the BindingListener is unbound as you say from the session, why would this subsequently cause a Tomcat exception? Wouldn't it invalidate the session and continue normally? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
