Thanks for your reply Tim. I'm aware that there is support for persistent sessions but I don't think that this will help me solving my problems: 1. we can't effort to access the DB for every request! 2. you cannot reload the session information from the DB when the class definition on tomcat has changed (correct me if I'm wrong). 3. this would still mean that I would have to shutdown the application for some time making it impossible for anybody to access it until I restart it.
I like your second idea though... clustering tomcat. The only problem I'm having when looking at this scenario is: What happens after the 1st instance is shutdown, the new code deployed and the application is restarted? That would mean that I got TWO tomcat instances up an running trying to replicate session data based on DIFFERENT class definitions, wouldn't it. Can I stop and reactivate session replication at runtime? Thanks for your help!!! Thomas -----Urspr�ngliche Nachricht----- Von: Tim Funk [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 25. M�rz 2004 17:14 An: Tomcat Users List Betreff: Re: need for deployment strategy without terminating user sessions Tomcat should be saving all session data to a serializable file. So you can persist session across an application restart. You can also (in tomcat 5) - use the clustering capability. You can use JDBC to persist sessions. OR You can not put stuff critical to a session and persist in another manner and save non-critical stuff in the session. -Tim Hubbert, Thomas wrote: > Hi, > I need some help on how to deploy applications on tomcat without terminating > all the user sessions (by stopping and restarting the application). At the > moment I can't see how this could be possible (not even with the help of > session replication). Is there any feature in tomcat or modjk which could > help me achieve this task? > --------------------------------------------------------------------- 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]
