>> As long as you shut down Tomcat gracefully, the standard session manager *does* save sessions across a restart, along with all of your session attributes -- but ONLY IF you make them serializable.
Our attributes are implementing serializable but it still doesn't appear to be saving and reloading them when I shutdown and restart webapps using the manager webapp. Though when I shutdown at the command prompt it does indeed create a bunch of *.ser files but when I restart tomcat the session attributes that I saved prior to shutdown aren't there though the manager webapp lists the same number of activate session as before shutdown. What am I missing? Thanks, Matt -----Original Message----- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 23, 2002 2:21 PM To: Tomcat Users List Subject: Re: Persistent Sessions On Wed, 23 Jan 2002, Matt Goyer wrote: > Date: Wed, 23 Jan 2002 14:14:14 -0500 > From: Matt Goyer <[EMAIL PROTECTED]> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Persistent Sessions > > I know that the docs warn 'Use of this Manager implementation has not > been thoroughly tested, and should be considered experimental!' but > has anyone tried using persistent sessions on a production site? > There are definitely some outstanding bugs in this code. > Alternatively, without persistent sessions is there a way to restart > tomcat without losing all the active sessions? As long as you shut down Tomcat gracefully, the standard session manager *does* save sessions across a restart, along with all of your session attributes -- but ONLY IF you make them serializable. > > Thanks, > Matt > Craig -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
