=0A=0A=0A=0A=0A________________________________=0AFrom: Rhonny David <rhonn=
ydavid@yahoo.com>=0ATo: Tomcat Users List <users@tomcat.apache.org>=0ASent:=
Thu, January 20, 2011 10:34:51 PM=0ASubject: Re: Tomcat 6 sessino timeout =
problem=0A=0A=0A=0A=0AWhen our application forces to terminate a=A0user ses=
sion explicitly, =0A=A0then=A0session listener=A0logs print as follows:=0A=
=0A12:16:37,812=A0 INFO [http-8080-24] Log1:9 - SessionCounter | =0Asession=
Destroyed(HttpSessionEvent se) | Start=0A12:16:37,812=A0 INFO [http-8080-24=
] Log1:9 - SessionCounter | =0AsessionDestroyed(HttpSessionEvent se) |=0A=
=0ABut when a user session terminates automatically, then session listerner=
logs =0Aprint as follows:=0A=0A12:20:26,921=A0 INFO [ContainerBackgroundPr=
ocessor[StandardEngine[Catalina]]] =0ALog1:9 - SessionCounter | sessionDest=
royed(HttpSessionEvent se) | Start=0A12:20:26,921=A0 INFO [ContainerBackgro=
undProcessor[StandardEngine[Catalina]]] =0ALog1:9 - SessionCounter | sessio=
nDestroyed(HttpSessionEvent se) | =0A=0A=0AFrom the log statements, =0A[Con=
tainerBackgroundProcessor[StandardEngine[Catalina]]]=A0 I am considering th=
at =0Athis is the conainer forced session termination. Now about your secon=
d point of =0Aresetting the session timeout, I have rechechcked the applica=
tion code but there =0Aisn't any code implemented to reset the session time=
out at runtime.=0A=0A=0ARegards,=0ADavid=0A=0A=0A=0A_______________________=
_________=0AFrom: "Caldarale, Charles R" <Chuck.Caldarale@unisys.com>=0ATo:=
Tomcat Users List <users@tomcat.apache.org>=0ASent: Thu, January 20, 2011 =
7:28:44 PM=0ASubject: RE: Tomcat 6 sessino timeout problem=0A=0A> From: Rho=
nny David [mailto:rhonnydavid@yahoo.com] =0A> Subject: Tomcat 6 sessino tim=
eout problem=0A=0A> We are facing session termination problem in Tomcat 6.0=
.29. In web.xml of our =0A> application, we have configured session timeout=
as 60 minutes, but tomcat is =0A> giving no respect to it, rather it rando=
mly terminates user session. We have =0A> implemented the HttpSessionListen=
er and we have found in application logs that =0A=0A> session sessionDestro=
yed method is called by a background tomcat process for =0A>the =0A>=0A> se=
ssion of user 333:=0A=0AWhat makes you think it's a background Tomcat threa=
d (not process) doing the =0Acall?=0A=0AMost likely, it's your code that is=
either explicitly destroying the session or =0Aresetting the timeout value=
.=0A=0A- Chuck=0A=0A=0ATHIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR O=
THERWISE PROPRIETARY =0AMATERIAL and is thus for use only by the intended r=
ecipient. If you received =0Athis in error, please contact the sender and d=
elete the e-mail and its =0Aattachments from all computers.=0A=0A=0A=0A----=
-----------------------------------------------------------------=0ATo unsu=
bscribe, e-mail: users-unsubscribe@tomcat.apache.org=0AFor additional comma=
nds, e-mail: users-help@tomcat.apache.org=0A=0A=0A
|