Discussion:
session-timeout vs. maxInactiveInterval
Lynn Hollerman
2009-06-25 15:01:21 UTC
Permalink
Question. I have been looking around the Net for information about the
items in the subject and tomcat; it appears that they are actually the
same thing(I'm not sure I'm understanding the docs correctly). So then,
what is the difference between the <session-timeout> that's set in a
tomcat's web.xml or an application's web.xml and the
"maxInactiveInterval" attribute of <Manager> in the context.xml file for
a particular application? Are these values interchangable, or does one
supercede the other?

Thanks!
--
Lynn Hollerman.
Office of Information Systems
University of Louisiana - Lafayette
337-482-6466
Caldarale, Charles R
2009-06-25 18:28:48 UTC
Permalink
Subject: session-timeout vs. maxInactiveInterval
I have been looking around the Net for information about
the items in the subject and tomcat; it appears that they
are actually the same thing
Pretty much. The <Manager> setting is used if the web.xml does not contain a <session-timeout> value. Note the following from the servlet spec description of <session-timeout>:

"If this element is not specified, the container must set its default timeout period."

Since Tomcat supplies a <session-timeout> element in the global conf/web.xml, you would have to remove that before the <Manager> setting became effective.

- 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.
Loading...