There was a recient post on this where someone else had a similar problem. It turned out in her case to be an AJAX request being made in the background which kept the session alive.
I can't seem to find a link to the thread in the archives but most of the advise given there for testing should be appropriate to this thread. On Thu, Sep 30, 2010 at 7:13 AM, Caldarale, Charles R <chuck.caldar...@unisys.com> 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. > > - 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 unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
