Regardless whether the user leave the browser idle or close the browser, as long as the user access the site from an IP that is inside of client's network, the seesion won't time out. By doing the same thing from outside IP, the session timeout correctly.
In both cases, the access log does NOT have anything logged other than the those actions when user were actually accessing the site. So I think there is no extra traffic being sent. If you are talking about any other possibilities to reset the session time out, could you please be more specific? Thank you! Jing ________________________________ From: Rainer Jung <rainer.j...@kippdata.de> To: Tomcat Users List <users@tomcat.apache.org> Sent: Thu, September 30, 2010 2:16:53 AM Subject: Re: session won't timeout 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
