Thanks for the reply. That's kind of what I suspected, but couldn't find anything that stated so....
> -----Original Message----- > From: mech [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 27, 2003 1:32 PM > To: 'Tomcat Users List' > Subject: RE: Session Timeout - Who has the final decision? > > > IMHO: Your web app web.xml overrides Tomcat's web.xml. Your > application > code overrides both. > > > > > I've checked the Tomcat-User and Struts-User archives for an > > answer to this, but am still not sure of the answer. Given > > that I can set a session timeout interval in Tomcat's > > configuration file (web.xml), the web application itself > > (web.xml), and also by setting > > 'session.setMaxInactiveInterval(#secs)', who wins? In other > > words, if I have the following: > > > > Tomcat timeout is 30 minutes > > Web Appl. timeout is 45 minutes > > session.setMaxInactiveInterval 3600 seconds (or 60 minutes) > > > > does the users session 'live' for the full 60 minutes? Or > > does one of the other settings take precedence? > > > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > This transmission (and any information attached to it) may be confidential and is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient or the person responsible for delivering the transmission to the intended recipient, be advised that you have received this transmission in error and that any use, dissemination, forwarding, printing, or copying of this information is strictly prohibited. If you have received this transmission in error, please immediately notify LabOne at the following email address: [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
