Thanks to Charles and Edmond for replying.
The problem was actually in my code. Tomcat destroyed the session, but
when calling sessionDestroyed()
(before the session is completely destroyed), a user bean that was
expected was already null.
The bottom line: session-timeout does work properly for tomcat 5.5.20!
Thanks so much,
Oren
Caldarale, Charles R wrote:
From: Oren Livne [mailto:[EMAIL PROTECTED]
Subject: Problems with tomcat session timeout on linux
The problem: some times users log in and then close their
browser window (at least I assume so), but tomcat never
destroys their session. The session-timeout parameter is
set to 30 in web.xml.
Is there any possibility of code in the webapp calling
setMaxInactiveInterval() to inhibit timeouts?
Is it possible that some request/response never finished processing and
is still hanging around for these hung sessions?
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
======================================================================
Oren Livne, Ph.D.
Research Assistant Professor of Mathematics
RUReady Software Architect
Academic Outreach and Continuing Education
1901 East South Campus Dr., Room 2197-D
University of Utah, Salt Lake City, UT 84112-9399
Tel : (801) 581-6831 Cell: (801) 631-3885 Fax: (801) 585-5414
Email: [EMAIL PROTECTED] Web: http://ruready.net/oren
======================================================================
