On Tue, 25 Jun 2002, Galbreath, Mark wrote: > That's pretty weird - never noticed that omission in the 2.2 and 2.3 > specs. AFAIK, if the session times out, all session variables are > dereferenced and eligible for garbage collection. You may be able > to explicitly dereference objects before the session is terminated > via HttpSessionBindingListener in 2.2.
FWIW, I don't think HttpSession.invalidate() should be called on a session timeout. They are different ways for ending a session, HttpSession.invalidate() is the programmatic way for ending a session. > -----Original Message----- > From: Ivanco Maros [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, June 25, 2002 11:28 AM > > It seams, that tomcat does not call HttpSession::invalidate() > method after session timeout. Is it bug or feature? I have not found > in spec what should happen with session after its timeout. Is there > a way to call user code after session timeout using 2.2 API? Or, at > least to ensure that objects in session will be garbage collected? Milt Epstein Research Programmer Systems and Technology Services (STS) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
