________________________________
From: Rhonny David <rhonnyda...@yahoo.com>
To: Tomcat Users List <users@tomcat.apache.org>
Sent: Thu, January 20, 2011 10:34:51 PM
Subject: Re: Tomcat 6 sessino timeout problem
When our application forces to terminate a user session explicitly,
then session listener logs print as follows:
12:16:37,812 INFO [http-8080-24] Log1:9 - SessionCounter |
sessionDestroyed(HttpSessionEvent se) | Start
12:16:37,812 INFO [http-8080-24] Log1:9 - SessionCounter |
sessionDestroyed(HttpSessionEvent se) |
But when a user session terminates automatically, then session listerner logs
print as follows:
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) |
From the log statements,
[ContainerBackgroundProcessor[StandardEngine[Catalina]]] I am considering that
this is the conainer forced session termination. Now about your second point of
resetting the session timeout, I have rechechcked the application code but
there
isn't any code implemented to reset the session timeout at runtime.
Regards,
David
________________________________
From: "Caldarale, Charles R" <chuck.caldar...@unisys.com>
To: Tomcat Users List <users@tomcat.apache.org>
Sent: Thu, January 20, 2011 7:28:44 PM
Subject: RE: Tomcat 6 sessino timeout problem
> From: Rhonny David [mailto:rhonnyda...@yahoo.com]
> Subject: Tomcat 6 sessino timeout problem
> 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:
What makes you think it's a background Tomcat thread (not process) doing the
call?
Most likely, it's your code that is either explicitly destroying the session or
resetting the timeout value.
- 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
