Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 91719 invoked from network); 20 Dec 2002 15:35:42 -0000 Received: from exchange.sun.com (HELO nagoya.betaversion.org) (192.18.33.10) by daedalus.apache.org with SMTP; 20 Dec 2002 15:35:42 -0000 Received: (qmail 3420 invoked by uid 97); 20 Dec 2002 15:36:33 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 3404 invoked by uid 97); 20 Dec 2002 15:36:32 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 3392 invoked by uid 98); 20 Dec 2002 15:36:32 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <399E1F52E73BD41194A800D0B74A08AB01E4DDFF@skipper.cincom.com> From: "Cox, Charlie" To: 'Tomcat Users List' Subject: RE: Session timeout setting (Getting desperate) Date: Fri, 20 Dec 2002 10:29:16 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N did you have any errors in the log file? It may be something as simple as not putting the in the correct order in the web.xml Charlie > -----Original Message----- > From: Kenny G. Dubuisson, Jr. [mailto:kdubuisson@kcmria.com] > Sent: Thursday, December 19, 2002 3:51 PM > To: Tomcat Users List > Subject: Re: Session timeout setting (Getting desperate) > > > 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." > To: "Tomcat Users List" > 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" > > To: "Tomcat Users List" > > 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 > || 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: > > > > > >For additional commands, e-mail: > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Fabio Mengue - Centro de Computacao - Unicamp > > > fabio@ccuec.unicamp.br fabio@unicamp.br > > > ---------------------------------------------------------------- > > > pi seconds is a nanocentury. - Tom Duff > > > > > > > > > > > > -- > > > To unsubscribe, e-mail: > > > > > For additional commands, e-mail: > > > > > > > > > > > -- > > To unsubscribe, e-mail: > > > For additional commands, e-mail: > > > > > > -- > To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: