Just for a test, I tried moving the web.xml file in the $CATALINA_HOME/conf directory to my application's WEB-INF directory and set the session-timeout setting to >60. Restarted Tomcat and then my application quit working (wouldn't even load the first JSP page). Needless to say I removed the web.xml file from my application and restarted Tomcat to get my app back working.
Still no luck in fixing the default session timeout in Tomcat. Any ideas whatsoever would be very much appreciated...I was supposed to have this fixed yesterday and I'm totally out of ideas. Thanks, Kenny ----- Original Message ----- From: "Kenny G. Dubuisson, Jr." <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Thursday, December 19, 2002 11:25 AM Subject: Re: Session timeout setting > I'm running Tomcat 4.0.5. Hope this helps. Thanks, > Kenny > > ----- Original Message ----- > From: "Fabio Mengue" <[EMAIL PROTECTED]> > To: "Tomcat Users List" <[EMAIL PROTECTED]> > Sent: Thursday, December 19, 2002 11:13 AM > Subject: Re: Session timeout setting > > > > On Tomcat 4.0.x, you had a Manager property for this (in server.xml, > > called |maxInactiveInterval|). Docs say **"The value for this property > > is inherited automatically if you specify a |<session-timeout>| element > > in the web application deployment descriptor (|/WEB-INF/web.xml|)." > > (http://jakarta.apache.org/tomcat/tomcat-4.0-doc/config/manager.html) > > > > I just looked 4.1.x docs > > (http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/manager.html) > > and the property is gone :) What version are you using ? Perhaps now it > > MUST be set on web.xml... > > > > I have a problem like yours. Development team will release an > > application soon that will require users to have sessions that last more > > that 1 hour; it's much much easier (for them) to just create a session > > and configure Tomcat to hold it for a whole day. Scalability is not on > > their minds, of course :) > > > > I think that has to be another way, something like Persistent Manager > > Implementation. > > > > Anyone knows a better way to solve this problem ? > > > > Thanks a lot, > > > > F. > > > > Kenny G. Dubuisson, Jr. wrote: > > > > >Sorry to repost this but I'm kind of in a bind (got users about to lynch > me > > >which may or may not be a bad thing). Anyway...session ID's on my site > > >(using Tomcat) are getting regenerated after a user has been logged in > for > > >60 mins. I would like to change this to a higher value but don't know > where > > >to set it. I've read throught posts on this list and I've seen some > things > > >mention the web.xml file and its session-timeout setting but my web.xml > > >session-timeout setting is currently set to 30 mins in that file so that > > >can't be the proper setting that I'm looking for. > > > > > >Any ideas would be greatly appreicated. My users are upset that they > have > > >to re-login evey hour on an application that they use all day. Thanks in > > >advance, > > >Kenny > > > > > > > > >-- > > >To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > >For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > -- > > Fabio Mengue - Centro de Computacao - Unicamp > > [EMAIL PROTECTED] [EMAIL PROTECTED] > > ---------------------------------------------------------------- > > pi seconds is a nanocentury. - Tom Duff > > > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
