On 30.09.2010 07:13, Caldarale, Charles R wrote:
From: Jing Chen [mailto:jin...@yahoo.com]
Subject: Re: session won't timeout
The results are different - in one case, the session is
destroyed after 30 minutes; but in another case, the
session stay active.
First, look in Tomcat's logs to see if there's anything interesting in there
regarding failures that might affect the session. Second, use Tomcat's manager
app (or JConsole) to see what the timeout value of the sessions really is;
something in your webapp might have changed it from the default. Third, turn
on Tomcat's AccessLogValve to find out if the supposedly closed browsers are
still sending in requests. Fourth, use Wireshark or equivalent on the client
systems to see if any traffic is being sent to the Tomcat server, resetting the
session timer.
Yes, active the access log for Tomcat and change the default pattern to
also include %S and maybe even
"%S "%{Set-Cookie}o" "%{Cookie}i"".
That way you can easily track the sessions.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
