You need to implement either in memory session replication or persist the session in a database or a shared file system.
I have finally got my tomcat cluster working and session replication is functional. Randall -----Original Message----- From: Sng Wee Jim [mailto:[EMAIL PROTECTED] Sent: Monday, March 07, 2005 10:50 PM To: [email protected] Subject: tomcat load-balancing maintenance strategy? Hi, I am load-balancing tomcat 5.0.28 using JK1.2 / AJP1.3. For discussion, let's assume I have 2 tomcats (TomcatA and TomcatB) load-balanced. When I shutdown one of the tomcats (Tomcat B), future requests for TomcatB is correctly redirected and handled by the TomcatA. However, the original session on TomcatB is not passed over to TomcatA, and a re-login is required. My question: 1. Is it possible to pass the session information to TomcatA before shutting down TomcatB? For eg. we want to perform servers upgrade, so we down TomcatB, upgrade it, start TomcatB, before doing the same to TomcatA. - Jim ************************************************************************ The information in this email is confidential and is intended solely for the addressee(s). Access to this email by anyone else is unauthorized. If you are not an intended recipient, please notify the sender of this email immediately. You should not copy, use or disseminate the information contained in the email. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Capco. http://www.capco.com/ ************************************************************************ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
