tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aggarwal, Ajay" <>
Subject RE: how to keep session alive on the server side
Date Tue, 23 Nov 2010 21:15:22 GMT
I am little reluctant to use HttpSession.setMaxInactiveInterval() for couple of reasons:

1) I don't know ahead of time how long these operations will take. SO I don't have a good
value to set the MaxInactiveInterval to.
2) I need to design for my clients crashing or losing connectivity with me. So I can't use
a negative value either (i.e. never expires).

-----Original Message-----
From: Christopher Schultz [] 
Sent: Tuesday, November 23, 2010 4:08 PM
To: Tomcat Users List
Subject: Re: how to keep session alive on the server side

Hash: SHA1


On 11/23/2010 1:46 PM, Caldarale, Charles R wrote:
>> From: Aggarwal, Ajay [] 
>> Subject: how to keep session alive on the server side
>> I have a situation where client enters a long duration 
>> request and I need to keep the session alive for the 
>> client while this long duration request is going on.
>> Since this long duration request could be hours, I do
>> not want to change the default HTTP session timeout value.
> Does the client provide any indication that it's about to enter the
> "long duration" state?  If so, you can call
> HttpSession.setMaxInactiveInterval() for that particular session from
> whatever JSP, servlet, or filter receives the indication.


- -chris
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla -


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message