-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David,
On 1/20/2011 5:02 AM, Rhonny David wrote: > We are facing session termination problem in Tomcat 6.0.29. In web.xml of our > application, we have configured session timeout as 60 minutes, but tomcat is > giving no respect to it, rather it randomly terminates user session. We have > implemented the HttpSessionListener and we have found in application logs > that > session sessionDestroyed method is called by a background tomcat process for > the > session of user 333: See the logs sample: > > 12:20:26,921 INFO [ContainerBackgroundProcessor[StandardEngine[Catalina]]] > Log1:9 - SessionCounter | sessionDestroyed(HttpSessionEvent se) | Start > 12:20:26,921 INFO [ContainerBackgroundProcessor[StandardEngine[Catalina]]] > Log1:9 - SessionCounter | sessionDestroyed(HttpSessionEvent se) | User Id 333 Okay, so this confirms that sessionDestroyed is being called. > Can anyone help to identify the problem? Can you demonstrate the problem? For instance, can you show us a session creation time, last session access time, and sessionDestroyed call that don't make sense together? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk04g9gACgkQ9CaO5/Lv0PAgjwCfS+r1FUQFGp/eOdhK9BZXhYBZ hqwAoIgNqEkNkk8n3wuKzKec54pf2Nfs =ZZta -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
