Hi, I'm looking for a deployment strategy for my production server which enables me to deploy new code without terminating all the user sessions. I was thinking about using two tomcat 5 instances and set up in memory session replication, but I still don't know what to do after I stopped the first instance and deployed the new code. If I restart the app it would try to get the session information from the other tomcat instance running the old code, which would probably result in some exceptions, wouldn't it?! Can I deactivate (and reactivate) session replication at runtime?
Also is there any way on telling modjk (currently using version 1.2) not to send requests for new sessions but still forward already existing sessions (with a valid jvmroute) to the tomcat instance still running the old code version? This way I could shutdown the second tomcat after all the sessions are closed by the users (or timed out). Cheers Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
