On Mon, 27 Jan 2003, Jerry Jalenak wrote:
> Date: Mon, 27 Jan 2003 13:22:47 -0600 > From: Jerry Jalenak <[EMAIL PROTECTED]> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> > Subject: Session Timeout - Who has the final decision? > > Hi All, > > 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) > Whichever value is set last always wins. Presumably, if your app is explicitly setting this, it was done after the session was created (which is when the initial default value is applied). You can call setMaxInactiveInterval() on a given session instance as many times as you like, and the last value you set is always the one that will apply when the current request completes. > does the users session 'live' for the full 60 minutes? Or does one of the > other settings take precedence? Well, you could always *try* this and see for yourself too :-). > > TIA! > > Jerry Jalenak Craig -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
