Hi, Why don't you investigate the cause for your timeouts instead of jumping through hoops to apply band-aids? ;)
Consider an HttpSessionLister to track your sessions in a portable manner. Then you can zoom though the sessions and do whatever you want (e.g. invalidate or extend the timeout) as needed. Yoav Shapira Millennium Research Informatics >-----Original Message----- >From: Arun Prasad R [mailto:[EMAIL PROTECTED] >Sent: Friday, September 10, 2004 7:05 AM >To: Tomcat Users List >Subject: Re: Can session time be modified at runtime? > >hi > >if i don't control in application, >so i can not do session.setMaxInactiveInterval(600); > >but for that application i experience frequent timeout. is there any >other way, so that i need not to restart tomcat > >arun > >On Fri, 10 Sep 2004 11:59:39 +0100, Mike Fowler ><[EMAIL PROTECTED]> wrote: >> You could use the session instance method setMaxInactiveInterval which >> takes a single int paramter which is the maximum time in seconds between >> client requests before invalidation. >> >> For example, for ten minute timeout: >> >> session.setMaxInactiveInterval(600); >> >> >> -Mike Fowler >> "I could be a genius if I just put my mind to it, and I, >> I could do anything, if only I could get 'round to it" >> >> >> >> Tim Funk wrote: >> > The session timeout can be changed at runtime (sort of). If you change >> > web.xml - you would need to restart your webapp. This would cause a >> > brief outage while sessions are saved to ???. (Unless your using >> > clustering) >> > >> > If you really need this changed on the fly, this might be able to be >> > changed via JMX. (But I haven't checked) >> > >> > -Tim >> > >> > Arun Prasad R wrote: >> > >> >> hi >> >> >> >> in web.xml the following comment has been given >> >> <!-- You can set the default session timeout (in minutes) for all >> >> newly --> >> >> <!-- created sessions by modifying the value >> >> below. --> >> >> >> >> <session-config> >> >> <session-timeout>30</session-timeout> >> >> </session-config> >> >> >> >> after changing session-timeout will it be effective for sessions >> >> created thereafter? >> >> >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
