So it's a documentation bug then :-) --- "Shapira, Yoav" <[EMAIL PROTECTED]> wrote:
> > Hi, > Hmm, I think that note is very old. It was probably copied over > from > Tomcat 4. The PersistentManager hasn't had any bugs filed against > it > for months at least (and it's been around for years now) so it's > probably in good shape. > > Yoav Shapira http://www.yoavshapira.com > > > >-----Original Message----- > >From: Mark [mailto:[EMAIL PROTECTED] > >Sent: Thursday, November 04, 2004 2:14 PM > >To: Tomcat Users List > >Subject: RE: sessionS info persistence when restart Tomcat > > > >Here some info I found: > >http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/manager.html > > > >but...: > >------cut --------- > >Persistent Manager Implementation > > > >WARNING - Use of this Manager implementation has not been > thoroughly > >tested, and should be considered experimental! > > > >---- end cut ------ > > > >Can anybody confirm what is a status for Persistent Manager in > Tomcat > >5.0.X? is it stable, is it safe to use in production and if not > what > >are other options. > > > >and here another link with detailed info on Persistent Manager: > >http://www.devx.com/assets/download/6264.pdf > > > >Mark. > > > > > >--- Steve Kirk <[EMAIL PROTECTED]> wrote: > > > >> I had always thought all sessions were lost when the server > >> restarts. In > >> fact I just tried it and confirmed that (5.0.28). Are we maybe > >> talking > >> about 2 different things? > >> > >> I have nonstandard config (a very sparse server.xml, no explicit > >> Manager > >> configured in server/web/context xml), and I do not use TC > >> authentication/realms, I just use request.getSession(true) and > rely > >> on > >> cookies to track users. After a restart, the webapp has lost > track > >> of users > >> that were tracked right up to the restart. > >> > >> Is this the manager config ref you were talking about? > >> > http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/manager.html > >> > >> > >> I just read through it. If I've understood correctly, because > my > >> Manager is > >> not explicitly configured, I have a default session manager > >> implicitly. I > >> stopped the server and looked for the serialised session file > under > >> /work > >> but just found the usual .java and .class files and one file > called > >> tldCache.ser, no sessions.ser or anything that looks like a > >> serialised > >> session file. > >> > >> > -----Original Message----- > >> > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > >> > Sent: Thursday 04 November 2004 15:07 > >> > To: Tomcat Users List > >> > Subject: RE: sessionS info persistence when restart Tomcat > >> > > >> > > >> > > >> > Hi, > >> > Tomcat persists and reloads sessions on restart by default. > And > >> the > >> > default session timeout is 30 minutes. So you shouldn't have > to > >> do > >> > anything. > >> > > >> > Check out the Manager configuration reference (not the Manager > >> webapp) > >> > for more details and settings you can modify in this area. > >> > > >> > Yoav Shapira http://www.yoavshapira.com > >> > > >> > > >> > >-----Original Message----- > >> > >From: Mark [mailto:[EMAIL PROTECTED] > >> > >Sent: Thursday, November 04, 2004 10:04 AM > >> > >To: [EMAIL PROTECTED] > >> > >Subject: sessionS info persistence when restart Tomcat > >> > > > >> > >Hi, > >> > > > >> > >Is it possible to save sessions info, so when Tomcat restarts > >> all > >> > >previously active sessions will be loaded. > >> > > > >> > >I'm trying to prevent user's re-login when Tomcat goes down > for > >> short > >> > >period (5-15 minutes) of time. > >> > > > >> > >Thanks, > >> > >Mark > >> > > > >> > > > >> > > > >> > >__________________________________ > >> > >Do you Yahoo!? > >> > >Check out the new Yahoo! Front Page. > >> > >www.yahoo.com > >> > > > >> > > > >> > > > >> > > >> > >>--------------------------------------------------------------------- > >> > >To unsubscribe, e-mail: > >> [EMAIL PROTECTED] > >> > >For additional commands, e-mail: > >> [EMAIL PROTECTED] > >> > > >> > > >> > > >> > > >> > This e-mail, including any attachments, is a confidential > >> > business communication, and may contain information that is > >> > confidential, proprietary and/or privileged. This e-mail is > >> > intended only for the individual(s) to whom it is addressed, > >> > and may not be saved, copied, printed, disclosed or used by > >> > anyone else. If you are not the(an) intended recipient, > >> > please immediately delete this e-mail from your computer > >> > system and notify the sender. Thank you. > >> > > >> > > >> > > >> > >--------------------------------------------------------------------- > >> > To unsubscribe, e-mail: > >> [EMAIL PROTECTED] > >> > For additional commands, e-mail: > >> [EMAIL PROTECTED] > >> > > >> > > >> > >> > >> > >> > >--------------------------------------------------------------------- > >> To unsubscribe, e-mail: > [EMAIL PROTECTED] > >> For additional commands, e-mail: > >> [EMAIL PROTECTED] > >> > >> > > > > > > > > > >__________________________________ > >Do you Yahoo!? > >Check out the new Yahoo! Front Page. > >www.yahoo.com > > > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > This e-mail, including any attachments, is a confidential business > communication, and may contain information that is confidential, > proprietary and/or privileged. This e-mail is intended only for > the individual(s) to whom it is addressed, and may not be saved, > copied, printed, disclosed or used by anyone else. If you are not > the(an) intended recipient, please immediately delete this e-mail > from your computer system and notify the sender. Thank you. > === message truncated === __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
